AR Clerk
Prepares local invoices, reviews cash proposals and applies permitted receipts. Cannot replace Controller write-off approval.
Give each person the customer and decision scope their work needs.
Summarised from the authored role permissions. Scope restrictions such as “own records” still apply; these symbols do not indicate completeness or runtime access.
| Table | Controller / CFO | AR Manager | AR Clerk | Sales Rep | Customer | Viewer |
|---|---|---|---|---|---|---|
| master | ||||||
Customers | —No table-specific permission stated | View: View unmasked Customers.CreditLimit | —No table-specific permission stated | —No table-specific permission stated | —No table-specific permission stated | —No table-specific permission stated |
| transaction | ||||||
CreditMemos | Specific actions: Approve CreditMemos above the AR Manager threshold | —No table-specific permission stated | —No table-specific permission stated | —No table-specific permission stated | —No table-specific permission stated | —No table-specific permission stated |
Prepares local invoices, reviews cash proposals and applies permitted receipts. Cannot replace Controller write-off approval.
Maintains collection policies, investigates disputes, manages holds and requests write-offs. Credit approval follows the configured threshold.
Owns the financial review, higher-tier adjustments and write-off decisions. Reconciles the AR population to its ledger owner.
Reads assigned-customer aging within account-owner scope.
Sees only their own permitted invoices and payment context.
Receives the intended aggregate read-only reporting scope.
Configures identities and integration access; administrative access is not permission to replace an independently assigned financial decision.
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 thresholdRead Customers.CreditLimit, PaymentsReceived.BankAccount, and BankFeedTransactions.BankAccount (unmasked)Sign off on ARAgingSnapshots at period closeCannot edit Invoices, PaymentsReceived, or CreditMemos directly — that's AR Clerk / AR Manager scopethe role is review and approval, not data entryWrite-off approval waits for the controller / cfo.
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)Read on Invoices, InvoiceLines, PaymentsReceived, PaymentApplications, BankFeedTransactions, ARAgingSnapshotsView unmasked Customers.CreditLimitCannot post WriteOffs to Approved (Controller only)Write-off approval waits for the controller / cfo.
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)CRUD on PaymentsReceived and PaymentApplications — including reviewing and confirming the auto-matched proposals from payment-application-auto-matchCRUD on CreditMemos and CreditMemoLines while Status IN (Draft) (AR Manager approves)Read on BankFeedTransactions, DunningEvents, DunningPolicies, Disputes, Customers, BillingTerms, InvoiceTemplatesTrigger ad-hoc dunning sendsRead Customers.CreditLimit maskedAccount-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 dataCannot edit anything in this app| 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 |
The buyer. Implicit role accessed through the customer payment portal — sees own open Invoices, can pay via the fin-payments-issued portal link, downloads own Invoices and Statements.
Read on own Invoices and InvoiceLines (filtered by Customer = self)Read on own PaymentsReceived and PaymentApplicationsInitiate payment via portal link (handled by fin-payments)Cannot see other Customers, internal notes, dunning history, credit limit, or any AR Manager / AR Clerk surfacesNo write access on AR tables — payments flow through fin-payments and create PaymentsReceived here on clearingExecutive read-only on aging and DSO. The owner, board member, or external auditor seat.
Read on Invoices, Customers (financial fields masked except OpenARBalance), ARAgingSnapshots, CollectionsCases, WriteOffs, DunningEvents, and all reportsCannot see Customers.CreditLimit, PaymentsReceived.BankAccount, or BankFeedTransactions.BankAccountCannot edit anything| 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 |
Apply customer ownership, field masking and action permissions consistently to lists, exports, references and APIs. Test both permitted and rejected requests before rollout. Bank and processor references retain their sensitive-field controls.
Systems administrator. Owns configuration, integration health, and user provisioning for the AR system. Not a day-to-day AR operator.
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.
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.
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.
Account-owner read-only on own Customers' AR. Nudges the buyer when a deal goes overdue without exposing GL detail.
The buyer. Implicit role accessed through the customer payment portal — sees own open Invoices, can pay via the fin-payments-issued portal link, downloads own Invoices and Statements.
Executive read-only on aging and DSO. The owner, board member, or external auditor seat.
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.