Create an invoice manually
Create an invoice yourself when you need to enter its fields instead of sending a document through normal intake.
Who can do this
You need the company:invoice:create permission.
Before you start
Decide whether the finished invoice needs a source document. You cannot attach one after you create the invoice without it.
Create an invoice with a source document
- Open Invoices in the left sidebar.
- Select the separate Manual entry button in the page header. It opens
/invoices/new. - Find Attach Source Document in the document area of the draft.
- Check the supported-file message: PDF, image, spreadsheet, or DOCX up to 50.0 MB.
- Select Choose File, then choose one file from your computer.
- Enter the header fields and invoice lines configured for your company while you compare them with the source preview.
- Select Create Invoice.
With the standard invoice record label, the draft shows Invoice and Drafting Invoice. A company with a different configured record label may show that label instead.
Create an invoice without a source document
- Open the manual entry page with Manual entry.
- Enter the required header fields and invoice lines.
- Select Create Invoice.
- Read the confirmation Create invoice without a source document?
- Confirm only after you read Manually created records cannot attach a document after creation.
- Select Create.
If you may need the source document for review or audit work, attach it before you create the invoice. The no-document confirmation cannot be undone by attaching a file later.
What you should see
Clerked opens the created invoice in the normal review workspace. The invoice uses your company schema's header fields, stacked line sections, and validation rules.
If something goes wrong
- If Manual entry is missing, ask an administrator to check your
company:invoice:createpermission. - If the file is rejected, check that it matches the types and 50.0 MB limit shown under Attach Source Document.
- If Create Invoice remains unavailable, review the draft for required fields and line-level validation errors.