Source ownership
The project billing service issues and financially owns its invoice. The AR collection reference carries the source invoice, current version and confirmed open balance; it cannot issue another invoice or revenue journal.

Follow up on project invoices while preserving the original billing owner.
Follow up on project invoices while preserving the original billing owner. Accounts Receivable System brings the relevant customer balances, collection decisions and receipt evidence into the shared workspace. Configure the source ownership and access boundaries before migration.
The project billing service issues and financially owns its invoice. The AR collection reference carries the source invoice, current version and confirmed open balance; it cannot issue another invoice or revenue journal.
Send credit or application requests to the billing owner and wait for its actual result. An accepted request is not a completed balance change, and a stale callback cannot replace the latest confirmed version.
Declare which service owns dunning for the selected population. Keep shared invoice references and communication history so a customer does not receive duplicate reminders from two systems.
Source ownership · Adjustment handoffs · Customer communications
Same records, same gates. The configuration changes how the process runs for this team.
The operational role — the day-in / day-out AR seat. Drafts and sends Invoices, applies PaymentsReceived against open Invoices, processes CreditMemos under threshold, sends manual dunning when a Customer-specific situation calls for it.
CRUD on Invoices and InvoiceLines while Status IN (Draft, Sent)Trigger Status: Draft → Sent (fires invoice-send and gl-post-on-invoice-send)CRUD on RecurringInvoiceSchedules (cannot delete an Active schedule without AR Manager)Owns the operational AR machine. Configures dunning policies, manages collections cases, releases credit holds, and approves credit memos under threshold. Escalates write-offs to the Controller.
CRUD on Customers (AR fields — CreditLimit, DefaultDunningPolicy, DefaultBillingTerm, StatementCadence), DunningPolicies, Disputes, CollectionsCases, CreditHolds, LateFees (waive)CRUD on CreditMemos (approve up to threshold)CRUD on WriteOffs as Draft → PendingApproval (routes to Controller)Write-off approval waits for the controller / cfo.
Owns the AR function. Approves WriteOffs, signs off on the period-end aging, and reviews DSO and bad-debt trend. The named approver on the GL post handoff to fin-accounting.
Full read on every table in the appCRUD on WriteOffs (sole approver — PendingApproval → Approved)Approve CreditMemos above the AR Manager thresholdAccount-owner read-only on own Customers' AR. Nudges the buyer when a deal goes overdue without exposing GL detail.
Read on Customers where Customer.AccountOwner = selfRead on Invoices, PaymentsReceived, ARAgingSnapshots, DunningEvents, CollectionsCases, CreditHolds scoped to those CustomersCannot see Customers.CreditLimit (masked), PaymentsReceived.BankAccount (masked), or any other Customer's data| Name | Billing Email | Open ARBalance | On Credit Hold | Statement Cadence |
|---|---|---|---|---|
| Customer 225 | [email protected] | 10,521.65 | 31,640.35 | None |
| Customer 963 | [email protected] | 15,343.56 | 41,567.43 | Monthly |
| Customer 858 | [email protected] | 23,142.93 | 22,056.10 | Quarterly |
| Customer 559 | [email protected] | 32,768.01 | 3,000.33 | None |
| Customer 905 | [email protected] | 8,853.39 | 12,102.19 | Monthly |
| Customer 487 | [email protected] | 29,178.53 | 40,547.75 | Quarterly |
Give overdue balances a clear next action and accountable owner.
Send clear invoices and keep every adjustment connected to its source.
Explain aging, collections and cash application with a consistent balance basis.
Keep customer terms and recurring billing ready for the next invoice.
Match incoming cash to the right invoices and explain every remainder.
Make credit decisions visible before they change a customer balance.
Open AR by Customer bucketed Current / 1-30 / 31-60 / 61-90 / 90+. Drills from total → AccountOwner → Customer → individual Invoice. Controller's daily landing report and the period-close reconciliation point with fin-accounting's AR subledger.
| Customer | As Of Date | Current Amount | Bucket1 To30 | Bucket31 To60 |
|---|---|---|---|---|
| CUS-193 | 16 Sep | 3,234.85 | 9,593.38 | 28,872.62 |
| CUS-207 | 22 Sep | 17,158.90 | 18,561.96 | 9,622.13 |
| CUS-230 | 14 Sep | 14,719.66 | 12,021.88 | 13,850.40 |
| CUS-040 | 29 Sep | 16,852.12 | 45,628.87 | 44,035.93 |
| CUS-037 | 13 Sep | 8,733.94 | 11,264.12 | 1,223.42 |
| CUS-114 | 07 Sep | 25,581.55 | 13,167.53 | 17,147.56 |
Per Customer: open AR, average days late, count of disputes, count of write-offs, active credit-hold flag, count of dunning sends. Drives the AR Manager's customer-level credit reviews.
| Hold Number | Customer | Reason | Held At | Held By |
|---|---|---|---|---|
| CH-13323 | CUS-058 | AgingBreach | 17 Sep | ZP |
| CH-38136 | CUS-214 | CreditLimitExceeded | 23 Sep | NS |
| CH-71438 | CUS-120 | ManualReview | 15 Sep | BB |
| CH-63837 | CUS-205 | BankruptcyFiling | 27 Sep | ES |
| CH-30101 | CUS-198 | DisputeOpenOverThreshold | 22 Sep | AU |
| CH-34469 | CUS-040 | AgingBreach | 18 Sep | MC |
Per DunningPolicy and per band: number of DunningEvents sent, payments received within N days of send, response and bounce rates. Used to tune policy thresholds and template copy.
No. AR maintains its receivables workflow and retains the connected ledger outcome. A draft journal reference is separate from confirmed posting.
Related questionYes, through read-only collection references with confirmed source balances. The project billing service remains the issuer and financial owner; local send and financial adjustment actions are disabled for that population.
Related questionNo. AR Clerk reviews the proposed customer and allocation. Only accepted cash applications affect local balances, within the receipt amount and invoice open balance.
Related questionYes. Keep the remainder on the customer account and allocate it deliberately later. A later application must not recognize the same receipt cash again.
Related questionCustomer access is restricted to the permitted records for their own identity. Verify lists, exports, references and APIs before inviting users.
Related questionNo. It records a stated cutoff population for reconciliation. The connected accounting system owns its actual period-close process.
Related questionConnect customer billing to the goods and delivery evidence you already use.
Keep agreed terms, recurring drafts and customer adjustments connected.
Follow up on project invoices while preserving the original billing owner.
Create your ERP.AI account and get started with Proto.
We use essential cookies to run the site and optional cookies for features, analytics, and relevant content. See Cookie policy
We use cookies to enhance your experience, analyze site traffic, and serve relevant content. By clicking "Accept All," you agree to our use of cookies. You can customize your preferences at any time.
Learn more about how we use cookiesThese 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.
These cookies enable additional features that enhance your experience, such as live chat, video playback, personalized content recommendations, and remembering user preferences.
These cookies help us understand how visitors interact with our site by collecting anonymous usage data. This allows us to measure performance, detect issues, and continuously improve the user experience.
These cookies allow us and advertising partners, including X, to deliver ads tailored to your interests. They track browsing habits across sites to provide relevant advertising and measure ad effectiveness.