Nirmion
HelpLog in Find a tool

Business Operations · THE NO-PANIC PLAN

Issue, track and reconcile small-business invoices

A dependable invoice process ties each amount to authorized work, uses the payment terms actually agreed with the customer, and follows the invoice all the way to a reconciled receipt. The fields and tax treatment that apply can depend on the contract, transaction and jurisdiction, so this guide does not claim one universal invoice format or legal due date. The Nirmion invoice tools draft and organize values you supply; they do not validate a contract, calculate jurisdiction-specific tax or collect customer payments.

MISSION Give a U.S. small business a repeatable outbound invoicing process from approved work evidence through payment reconciliation and orderly record retention.

Match every invoice to approved work and agreed terms

THE REAL-WORLD BIT

What happens outside this browser tab?

Match completed work to an approved contract/order; prepare and independently review the invoice; send it through the customer's approved channel with a clear due date; track delivery and receivable status with a polite follow-up plan; reconcile payment and retain the invoice with supporting records.

YOUR CHECKLIST, WITH FEWER DRAMATIC SIGHES

One step at a time.

Follow the order below. If a step names a Nirmion tool, its link is right there with it.

  1. 01

    Confirm the work, customer and authorization before billing

    Use the signed agreement, accepted quote, customer purchase order or other documented approval to confirm the legal customer name, billing contact, scope, quantities, milestones, accepted work, pricing, currency, deposit/retainer already paid and any reimbursable cost rules. Compare delivery evidence such as timesheets, shipment records or acceptance notes to the approved scope, and resolve change requests before billing rather than silently adding work. If the customer requires a portal, PO number, cost code, named approver or supporting document, confirm it before issuing. Keep customer account changes and bank-detail updates in a separate verified process; do not treat an email request to redirect funds as proof.

  2. 02

    Create an itemized invoice and review every calculation

    Assign the next unique invoice reference from your controlled numbering convention, then enter the issue date, seller and customer details, description of each good/service, quantity or period, agreed rate, subtotals, approved discount, deposit credit, applicable tax only when confirmed, total due, currency, payment instructions and the contract's actual due date/terms. Use the Invoice Generator (tool 176) to draft an itemized document and printable/CSV output; it does not determine what tax applies or reserve your invoice number. Have someone other than the preparer compare arithmetic, customer identity, PO, scope, currency, due date and bank/payment destination to source evidence. Do not add a late fee or change terms unless the governing agreement and applicable rules support it.

  3. 03

    Send the approved invoice through the customer's documented channel

    After the review, deliver the invoice using the channel the customer has approved, such as its procurement portal, named billing mailbox or agreed invoicing system. Include only the supporting records needed for acceptance, make the invoice reference and due date easy to find, and request a receipt/portal status when available. Before sending, confirm recipient addresses from an established contact list, especially if an email asks to change remittance details. Avoid placing bank account data, tax identifiers or customer confidential information in a broadly accessible folder. Record the sent timestamp, channel, recipient and delivery confirmation; if the invoice is rejected, preserve the rejection reason and correct the source record before issuing a clearly linked revision or credit.

  4. 04

    Track acceptance, due dates, disputes and follow-up actions

    Maintain one receivables register with invoice ID, customer, amount/currency, issue and contractual due dates, sent/accepted status, balance, last contact, next action and any dispute owner. Use the Invoice Due Date Calendar (tool 61438) to calculate nominal dates from the net terms and monthly issue date you enter; it is not a contract interpreter and its next-workday output may not match a customer's holiday or payment-processing rules. Send a courteous reminder before/after the agreed date based on your written policy, attach the original invoice, and ask a specific question when acceptance or a purchase-order match is blocking payment. Escalate a genuine scope/quality/tax dispute to the responsible person with the underlying evidence, not a duplicate invoice.

  5. 05

    Reconcile the actual receipt and close the record

    When a payment arrives, match it against the bank or payment-processor record and remittance advice, identify any short-pay, fee, withholding, credit or multi-invoice allocation, and update the outstanding balance only after the funds are confirmed. Send a receipt or paid confirmation if your agreement or customer process calls for one. The IRS says businesses should keep supporting records such as invoices, receipts, deposit information and books that clearly show income and expenses; retain the invoice, approval, acceptance evidence, payment proof and corrected versions together for the applicable retention period. Reconcile the receivables register to the accounting ledger on a regular schedule and review overdue balances without deleting the original audit trail.

THE HELPER CREW

Tools for the fiddly bits.

These are the currently published Nirmion tools matched to this guide. Open a tool page for its accepted inputs and limits.

RECEIPTS, PLEASE

Sources & review notes

Each source is linked to the steps it supports. Open it to check its scope and current guidance.

Source checked 2026-10-06