These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Accounts Receivable System
- Data model
The tables behind Accounts Receivable System
Accounts Receivable System ships with 20 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 20
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
Every table, by feature
- Customer billing5
- Invoices and credits6
- Cash application6
- Collections6
- Credit controls6
- Receivables reporting8
- Shared and settings1
- Customers
The AR-grain customer record. May shadow a CRM Account; this row carries the credit, billing, and dunning fields finance owns.
Linked to Billing terms, Dunning policies, Invoice templates, Employees (sales rep) - Billing terms
Catalog of payment terms. Net 15, Net 30, Net 60, Net 90, EOM, Prepay, Due on Receipt, plus optional late-fee rule.
- Invoice templates
Branded invoice render formats. Picks the logo, tax footnote language, and remit-to. One template per legal entity / division.
- Recurring invoice schedules
Subscription / retainer billing config. The recurring-invoice generation workflow walks these daily and materializes Invoices. Each occurrence is uniquely keyed by schedule and scheduled date; honor end date and credit holds, and preserve previous generated invoices when changing future terms.
Linked to Customers, Invoice templates, Billing terms - Credit holds
Customer-level credit hold. While Active, no new Invoices may be sent and no recurring invoice schedules generate for the Customer.
Linked to Customers, Employees (AR Manager)
- Invoices
The customer invoice — the AR atom. Header carries totals; detail lives in invoice lines.
Linked to Customers, Invoice templates, Billing terms, Recurring invoice schedules (when Type = Recurring) - Invoice lines
One line per item billed — product, service, milestone, or late-fee carry-forward.
Linked to Invoices - Credit memos
A credit issued against a Customer or a specific Invoice. Reduces AR; can be applied to an open Invoice or left as a standalone credit on account.
Linked to Customers, Invoices, Employees (AR Manager) - Credit memo lines
Per-line detail of a credit memo.
Linked to Credit memos - Customers
The AR-grain customer record. May shadow a CRM Account; this row carries the credit, billing, and dunning fields finance owns.
Linked to Billing terms, Dunning policies, Invoice templates, Employees (sales rep) - Disputes
A customer-raised dispute against an Invoice. Pauses dunning while open.
Linked to Invoices, Customers, Employees (AR Manager)
- Bank feed transactions
Read-stream from the bank API. Source for cash auto-application. Not an authoritative ledger record — consumed by payment-application-auto-match.
Linked to Payments received - Payments received
An incoming payment from a Customer. May be auto-created by the auto-match workflow from a bank feed transaction or manually keyed by an AR Clerk.
Linked to Customers, Bank feed transactions (when matched), Employees (AR Clerk) - Payment applications
Distributes a payment received across one or more Invoices (or leaves the remainder unapplied on the customer’s account).
Linked to Payments received, Invoices - Invoices
The customer invoice — the AR atom. Header carries totals; detail lives in invoice lines.
Linked to Customers, Invoice templates, Billing terms, Recurring invoice schedules (when Type = Recurring) - Credit memos
A credit issued against a Customer or a specific Invoice. Reduces AR; can be applied to an open Invoice or left as a standalone credit on account.
Linked to Customers, Invoices, Employees (AR Manager) - Write-offs
Uncollectible AR written off the books. Requires Controller approval; posts a JE in fin-accounting that contras the AR balance and hits Bad Debt Expense.
Linked to Invoices, Customers, Employees (AR Manager), Employees (Controller / CFO)
- Dunning policies
Per-Customer or default dunning policy. Defines aging-band thresholds, the email template per band, and the escalation contact.
- Dunning events
The audit trail of every dunning communication sent. One row per Invoice per band per send.
Linked to Invoices, Customers, Dunning policies - Collections cases
Escalated collections workflow. Opened when an Invoice crosses dunning policy band4 days or by AR Manager intervention.
Linked to Customers, Invoices (the trigger invoice), Employees (AR Manager), Employees (assigned AR Clerk or AR Manager) - Disputes
A customer-raised dispute against an Invoice. Pauses dunning while open.
Linked to Invoices, Customers, Employees (AR Manager) - Invoices
The customer invoice — the AR atom. Header carries totals; detail lives in invoice lines.
Linked to Customers, Invoice templates, Billing terms, Recurring invoice schedules (when Type = Recurring) - Customers
The AR-grain customer record. May shadow a CRM Account; this row carries the credit, billing, and dunning fields finance owns.
Linked to Billing terms, Dunning policies, Invoice templates, Employees (sales rep)
- Credit holds
Customer-level credit hold. While Active, no new Invoices may be sent and no recurring invoice schedules generate for the Customer.
Linked to Customers, Employees (AR Manager) - Late fees
Late fees applied per billing term late fee policy. Each late fee spawns a follow-on Invoice of
Linked to Invoices, Customers, Employees (AR Manager)Type: LateFeelinked back viaOriginalInvoice. - Write-offs
Uncollectible AR written off the books. Requires Controller approval; posts a JE in fin-accounting that contras the AR balance and hits Bad Debt Expense.
Linked to Invoices, Customers, Employees (AR Manager), Employees (Controller / CFO) - Invoices
The customer invoice — the AR atom. Header carries totals; detail lives in invoice lines.
Linked to Customers, Invoice templates, Billing terms, Recurring invoice schedules (when Type = Recurring) - Customers
The AR-grain customer record. May shadow a CRM Account; this row carries the credit, billing, and dunning fields finance owns.
Linked to Billing terms, Dunning policies, Invoice templates, Employees (sales rep) - Billing terms
Catalog of payment terms. Net 15, Net 30, Net 60, Net 90, EOM, Prepay, Due on Receipt, plus optional late-fee rule.
- AR aging snapshots
Period-frozen aging buckets per Customer. Written by the ar-aging-snapshot scheduled workflow on the last day of each period.
Linked to Customers - Invoices
The customer invoice — the AR atom. Header carries totals; detail lives in invoice lines.
Linked to Customers, Invoice templates, Billing terms, Recurring invoice schedules (when Type = Recurring) - Payments received
An incoming payment from a Customer. May be auto-created by the auto-match workflow from a bank feed transaction or manually keyed by an AR Clerk.
Linked to Customers, Bank feed transactions (when matched), Employees (AR Clerk) - Payment applications
Distributes a payment received across one or more Invoices (or leaves the remainder unapplied on the customer’s account).
Linked to Payments received, Invoices - Collections cases
Escalated collections workflow. Opened when an Invoice crosses dunning policy band4 days or by AR Manager intervention.
Linked to Customers, Invoices (the trigger invoice), Employees (AR Manager), Employees (assigned AR Clerk or AR Manager) - Dunning events
The audit trail of every dunning communication sent. One row per Invoice per band per send.
Linked to Invoices, Customers, Dunning policies - Write-offs
Uncollectible AR written off the books. Requires Controller approval; posts a JE in fin-accounting that contras the AR balance and hits Bad Debt Expense.
Linked to Invoices, Customers, Employees (AR Manager), Employees (Controller / CFO) - Customers
The AR-grain customer record. May shadow a CRM Account; this row carries the credit, billing, and dunning fields finance owns.
Linked to Billing terms, Dunning policies, Invoice templates, Employees (sales rep)
Migration order
- Customers, billing terms, invoice templates and dunning policies establish the reviewed billing basis.
- Invoices and invoice lines preserve local obligations or separately identified external collection references.
- Payments received, payment applications and bank feed transactions preserve receipt identities and accepted allocations.
- Credit memos, credit memo lines, Disputes, write-offs, late fees, credit holds and collections cases retain adjustments and decisions.
- Dunning events and AR aging snapshots preserve communications and cutoff evidence.
Balance rules
Local open balance deducts accepted cash, applied credits and posted write-offs once. Proposals cannot reduce it. External collection references use their confirmed external open balance and source version instead of mixing in local financial actions. Keep all corrections attributable to the original source.
Set up Accounts Receivable System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.