Esc

↑↓ move↵ openIndex · Pagefind
Accounting apps / Accounts Receivable

Accounts Receivable

Bill certified G702/G703 pay apps and five other billing methods, manage retainage receivable, collect with dunning, disputes and promises, and take online payments in the customer billing portal.

On this page

Accounts Receivable turns certified owner pay apps and other contract billings into invoices, tracks retainage receivable through closeout, and applies customer cash. Collections runs dunning, disputes and promises to pay, and customers can view and pay invoices in the customer billing portal. Every invoice, receipt and reversal needs an independent approver. Open it from the company app launcher under Accounting > Accounts Receivable; it appears when your accounting access includes it.

Who uses it
AR clerks prepare invoices and receipts and work collections; AR approvers approve, post, deposit, reverse and manage dunning and portal links; customers pay through the billing portal.
When
Each billing cycle; as payments arrive; at closeout for retainage.
What it holds
Invoices with revisions, receipts and allocations, deposits, credit memos, refunds, collection notes and activities, disputes, promises to pay, dunning policies and sends, portal billing links, online payments and closeout documents.

Key workflow

  1. Bill the pay app. For a progress contract, create the invoice from an approved owner pay app. The pay app is recalculated with the G702 math against retainage already billed and must reproduce its certified amount before the invoice is drafted. Download a G702/G703-style PDF of the certified pay app.
  2. Bill other contract types. Time and materials, cost-plus, unit price, GMP and milestone contracts bill from their approved billing terms. Terms changes are proposed by one person and approved by another before billing uses them.
  3. Approve, post and send. An independent approver approves the invoice, then it posts. Queue a posted invoice to email the billing contact with the PDF attached.
  4. Record and deposit cash. Record a receipt allocated to open invoice lines, approve and post it, then deposit posted receipts from undeposited funds to the bank in one entry.
  5. Follow collections. Work the collections worklist, let dunning policies send reminders, and record calls, disputes and promises to pay. Use aging as of any date and customer statements. Customers can see and pay their invoices in the customer billing portal.
  6. Bill in the customer’s currency. An invoice and its receipts can carry a foreign currency and exchange rate (by default the spot rate on the posting date). Collecting at a different rate posts the realized gain or loss automatically; see Foreign Currency.

Retainage receivable and closeout

Retainage is calculated separately on completed work and stored materials and tracked by contract. To bill held retainage, open a posted invoice and use Release retainage: Draft retainage release creates a retainage release invoice that is submitted, approved and posted like any invoice. An AR approver keeps each prime contract’s closeout checklist under Invoices > Contract closeout (or Contract closeout checklist on a posted contract invoice): manual requirements such as consent of surety, final waivers or punch list complete, marked received after review, and approved submittal revisions linked as evidence, which count only while they stay approved and current. A release that empties the contract’s open retainage, from a pay app or a retainage release invoice, is refused until every required item is complete; partial releases are not gated. Customer tax exemption certificates valid on the invoice date remove sales tax from pay-app invoices, and on a project with a job site, sales tax is computed per jurisdiction by the sales and use tax engine.

Collections and dunning

Collections is fully rule-based: no prediction, scoring model or AI. Open it under Accounting > Accounts Receivable > Collections.

  • Dunning. One policy per customer class, with steps at a number of days before or after the due date (for example −5, +1, +15, +30 and +60), each with its own email subject and body. Sends fall on business days, skip company holidays and wait out quiet hours in the accounting time zone. A step can also email the customer’s collector to escalate. The daily run sends each step for an invoice at most once, even when it is re-run or two runs overlap; after a pause only the latest due step goes out.
  • Dunning follows the edition. The Professional and Enterprise editions switch dunning on, adding the default policy only when the company has none; Essentials leaves it off. Applying an edition cannot switch dunning off while any open invoice is part-way through its reminder sequence, and switching it off needs a reason. You can still pause customers with a hold, or switch dunning off on the collections settings page, which is audited.
  • Pauses and suppression. No reminder goes out while an invoice is disputed, covered by an open promise to pay, or its customer is on hold. Paid and fully credited invoices are never reminded, and retainage is not collected until a release bills it.
  • Worklist. Customers with open current AR, ranked by open amount weighted by age and by risk (broken promises in the last year, and paying slower than terms). Disputed invoices are shown separately. Each customer has a collector, hold, next follow-up date, days to pay, and a log of calls, emails and notes.
  • Disputes and promises. A dispute has a reason code (pricing, quantity, quality, not received, duplicate, retainage, change order, documentation or other) and an amount, and moves the invoice into the aging’s Disputed column. A promise to pay has a date and amount, for named invoices or the whole customer, and is marked kept when posted receipts reach it within its window, or broken the day after the window closes.
  • Reports. Collection effectiveness index (CEI), days sales outstanding (DSO), promise-kept rate and dispute aging, with retainage left out of the receivables.

Customer billing portal and online payment

Billing pages are added to the existing customer portal; there is no separate sign-in. An AR approver links a customer’s portal grant to one AR customer, and revoking the link takes effect at once. The customer then sees only its own posted invoices billed on that grant’s project:

  • open invoices and pay apps, the statement and aging, and payment history;
  • invoice PDFs and the G702/G703 for a pay app;
  • a dispute form on each invoice, and a promise-to-pay form, both landing in the staff collections workbench;
  • online payment of selected current invoices by card or ACH.

Starting a payment creates a draft receipt against a clearing account. When the provider confirms it through a signed, replay-safe webhook, the receipt posts and applies the cash; if an invoice was paid meanwhile, the remainder lands as unapplied cash. A failed payment cancels the draft. Before any of these steps the books are checked against the provider: if the captured amount or currency differs from the charge, or a payout’s gross, fees and net differ from the payments it names, the payment is held with the reason, finance is alerted and nothing posts. The provider’s payout posts the net deposit and the processing fees and clears the clearing account, and the bank statement line matches it in the matching inbox. Optional surcharges and convenience fees are off by default; whether you may charge them depends on state law and card rules, which the software does not check.

Controls

  • Invoices, receipts, credit applications, deposits and refunds each need an approver who did not prepare or contribute to them.
  • Writes carry a request key, so a retried request returns the original document instead of a duplicate.
  • Collections reads are entity-scoped and refused to project-scoped grants. Disputes, promises, profiles and runs need AR entry rights; dunning settings, policies and portal billing links need AR approval rights.
  • Portal reads and writes are limited to the linked customer’s posted invoices on the grant’s project. Another customer’s or another project’s invoice answers exactly like an unknown one, and nothing is written. Portal mutations need the configured origin and the session CSRF token.
  • An online payment’s receipt is prepared by a dedicated portal user who cannot sign in and approved by the automation user, so maker-checker still holds. Each provider event is recorded once; a replayed or forged event changes nothing.
  • Posted documents are corrected by source-owned reversals that need an independent approver, a reason and an open period. Reconciled bank lines block a receipt reversal.

Current boundaries

For the full procedure, exceptions and examples, read the Accounts receivable workflow guide.

API operations

78 operations · 34 read · 44 write · base path /rest/v1.0/companies/{company_id}/accounting

  1. GET /ar/collections/disputesDisputes
  2. POST /ar/collections/disputesOpen a dispute on a posted invoice (arEnter)
  3. GET /ar/collections/disputes/{id}A dispute
  4. POST /ar/collections/disputes/{id}/resolveResolve or withdraw a dispute (arEnter)
  5. GET /ar/collections/paymentsOnline payments
  6. GET /ar/collections/payments/{id}An online payment
  7. GET /ar/collections/policiesDunning policies
  8. POST /ar/collections/policiesCreate a dunning policy (arApprove)
  9. PATCH /ar/collections/policies/{id}Replace a dunning policy's cadence (arApprove)
  10. GET /ar/collections/portal_accessCustomer portal billing links
  11. POST /ar/collections/portal_accessLink a customer portal grant to an AR customer (arApprove)
  12. POST /ar/collections/portal_access/{id}/revokeRevoke a billing link (arApprove)
  13. GET /ar/collections/promisesPromises to pay
  14. POST /ar/collections/promisesRecord a promise to pay (arEnter)
  15. POST /ar/collections/promises/{id}/cancelCancel an open promise (arEnter)
  16. POST /ar/collections/runRun collections now (arEnter)
  17. GET /ar/collections/settingsCollections and online payment settings
  18. PATCH /ar/collections/settingsUpdate collections settings (arApprove)
  19. GET /ar/collections/worklistPrioritized collections worklist
  20. GET /ar/customersList AR customers
  21. GET /ar/customers/{id}Customer open balances net of posted receipts and reversals; paginated invoice history
  22. GET /ar/customers/{id}/collection_notesLatest 100 collection notes for the customer in permitted entities.
  23. POST /ar/customers/{id}/collection_notesAdd a collection note (optional invoice and promise to pay). arEnter.
  24. GET /ar/customers/{id}/collectionsA customer's collections view
  25. PATCH /ar/customers/{id}/collectionsUpdate a customer's collections profile (arEnter)
  26. GET /ar/customers/{id}/statementCustomer statement: open posted invoices, unapplied cash and balance due, with the billing contact.
  27. POST /ar/depositsDeposit posted receipts held in UNDEPOSITED_FUNDS to a bank account as one journal (Dr bank / Cr undeposited funds). arApprove; idempotent by request_key.
  28. GET /ar/gmp_applications/{id}Get a GMP application
  29. PATCH /ar/gmp_applications/{id}Edit a GMP application
  30. POST /ar/gmp_applications/{id}/billBill a GMP application
  31. POST /ar/gmp_applications/{id}/certifyCertify a GMP application
  32. GET /ar/gmp_applications/{id}/packageGMP application owner package
  33. GET /ar/gmp_applications/{id}/registerGMP application cost register
  34. POST /ar/gmp_applications/{id}/returnReturn a GMP application
  35. POST /ar/gmp_applications/{id}/submitSubmit a GMP application
  36. POST /ar/gmp_applications/{id}/voidVoid a GMP application
  37. POST /ar/gmp_applications/{id}/withdrawWithdraw a GMP certification
  38. POST /ar/gmp_draws/{id}/decisionDecide a GMP draw
  39. GET /ar/gmp/statusGMP status of a project
  40. GET /ar/invoicesList scoped invoices (default 100, maximum 100 per page)
  41. POST /ar/invoicesCreate a draft; a retry with the same request key and payload returns the original invoice
  42. GET /ar/invoices/{id}Get scoped invoice
  43. PATCH /ar/invoices/{id}Replace current draft revision; all editors are excluded from approval
  44. GET /ar/invoices/{id}/attachmentsList attachments on a AR invoice
  45. POST /ar/invoices/{id}/attachmentsAttach a file to a AR invoice
  46. POST /ar/invoices/{id}/credit_applicationsApply a posted on-account credit memo to open invoice lines (Dr AR control / Cr receivable line). arApprove; idempotent by request_key.
  47. POST /ar/invoices/{id}/disputeFlag or clear a collections dispute on a posted invoice. Disputed invoices age in the Disputed column. arEnter.
  48. GET /ar/invoices/{id}/pdfInvoice PDF
  49. POST /ar/invoices/{id}/reverseAppend a source-owned reversal. Independent arApprove required. Identical retries return the original reversal.
  50. POST /ar/invoices/{id}/sendQueue a posted invoice for email to the customer's billing contact, with the invoice PDF attached.
  51. POST /ar/invoices/{id}/transitionSubmit, return to draft, independently approve, or post an invoice
  52. POST /ar/invoices/from_billingDraft an AR invoice from a non-progress billing
  53. POST /ar/invoices/from_payment_applicationBill a certified owner pay app in AR (once per pay app)
  54. GET /ar/payment_applications/{id}/pdfG702/G703 PDF of a certified owner pay app
  55. PUT /ar/prime_contracts/{id}/billing_methodSet a prime contract's billing method
  56. GET /ar/prime_contracts/{id}/billing_termsGet a prime contract's billing terms
  57. PUT /ar/prime_contracts/{id}/billing_termsPropose a prime contract's billing terms
  58. POST /ar/prime_contracts/{id}/billing_terms/approveApprove a prime contract's proposed billing terms
  59. GET /ar/prime_contracts/{id}/closeoutGet a prime contract's closeout documents
  60. PUT /ar/prime_contracts/{id}/closeoutSet a prime contract's closeout documents
  61. GET /ar/prime_contracts/{id}/gmp_applicationsList a GMP contract's applications
  62. POST /ar/prime_contracts/{id}/gmp_applicationsStart a GMP application
  63. GET /ar/prime_contracts/{id}/gmp_closeoutGMP close-out reconciliation
  64. GET /ar/prime_contracts/{id}/gmp_drawsList GMP contingency and allowance draws
  65. POST /ar/prime_contracts/{id}/gmp_drawsPropose a GMP contingency or allowance draw
  66. GET /ar/receiptsReceipt history, 50 per page
  67. POST /ar/receiptsRecord a fully allocated draft; matching request-key retries return the original receipt
  68. GET /ar/receipts/{id}Receipt detail and immutable applications
  69. POST /ar/receipts/{id}/applicationsApply a posted receipt's unapplied cash to open invoice lines, or transfer its allocations between lines. arApprove; idempotent by request_key.
  70. GET /ar/receipts/{id}/attachmentsList attachments on a AR receipt
  71. POST /ar/receipts/{id}/attachmentsAttach a file to a AR receipt
  72. POST /ar/receipts/{id}/reverseAppend a source-owned reversal. Independent arApprove required. Identical retries return the original reversal.
  73. POST /ar/receipts/{id}/transitionIndependently approve or post; balances are revalidated under the company lock
  74. GET /ar/receipts/open_itemsOpen original AR distributions for one customer/entity; pages over open invoices only, oldest due first
  75. GET /ar/refundsCustomer refunds, newest first (paginated).
  76. POST /ar/refundsDraft a refund of customer credit: a posted receipt's unapplied cash or an on-account credit memo. arEnter; idempotent by request_key.
  77. GET /ar/refunds/{id}Refund detail.
  78. POST /ar/refunds/{id}/transitionPost, cancel or reverse a customer refund.

Parameters, request and response fields, errors and a generated example for each operation are in the REST reference for this app. Read scopes, step-up and permissions in the Accounting API guide.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file