AR Accountant — Accounts Receivable
Department: Finance
Level: Operational
Primary objective: Collect money from customers — track invoices, record payments, reconcile bank statements, manage e-invoice compliance
What this role does
The AR Accountant is responsible for all customer collections: issues or verifies invoices, follows up on overdue payments, records incoming payments, reconciles bank statements, and ensures B2B invoices are correctly submitted to ANAF via e-invoicing. They are the first to know a customer is late on payment and the first to act.
Modules used daily
| Module | Where to find it | What you use it for |
|---|---|---|
| Invoices | Sales → Invoices | Main queue — sent, overdue, partially paid invoices |
| Payments | Sales → Payments | Record every incoming payment received |
| Bank Statement | Finance → Bank Statement | Reconcile received payments against bank statement |
| e-Invoice | Finance → e-Invoice | Submit B2B invoices to ANAF and monitor status |
| Credit Notes | Sales → Credit Notes | Process customer reversals and returns |
| Account Balances | Finance → Account Balances | View internal cash position |
| Clients | CRM → Clients | Verify customer tax data and payment history |
Daily routine
Morning — collections status
- Invoices → filter status "Overdue" (past due date) + "Partially Paid"
- Sort by days overdue descending — oldest first
- Invoices overdue > 7 days → send reminder (email from platform or phone call)
- Invoices overdue > 30 days → escalate to Sales Manager / CFO
Recording received payments
- Open the bank statement received from the bank (MT940 or CSV)
- Bank Statement → import the statement or manually add each received transaction
- For each bank entry → associate the corresponding invoice → invoice status changes to "Paid" or "Partially Paid"
- Unidentified payments (customer reference incorrectly written) → place on hold and investigate
e-Invoice ANAF (B2B customers with VAT number)
- e-Invoice → check the list of invoices with status "Pending" or "Validation Error"
- Invoices rejected by ANAF → identify the incorrect field → correct the invoice → resubmit
- Validated invoices → download the signed archive if you need the ANAF PDF
End of day — reconciliation
- Verify that all payments received today are recorded in the platform
- Does the balance in Bank Statement correspond to payments recorded in Payments? If not → identify the discrepancy
Key workflows
Workflow 1 — Record full payment from customer
Customer transfers the full amount
→ Receive bank notification (email or statement)
→ Sales → Payments → Add
→ Customer: select from list
→ Invoice: select the corresponding invoice
→ Amount, date, payment method (bank transfer)
→ Save → Invoice automatically moves to "Paid" status
→ Bank Statement reconciliation: associate the bank line with the recorded payment
Workflow 2 — Partial payment
Customer transfers partially (e.g. 60% of invoice)
→ Sales → Payments → Add
→ Amount: the amount actually received (not the total invoice value)
→ Invoice moves to "Partially Paid" status
→ Remaining balance visible on invoice
→ On second instalment → add another payment for the difference
→ At 100% completion → invoice moves to "Paid"
Workflow 3 — Customer doesn't pay — chasing overdue
Invoice overdue > 7 days
→ Open invoice → "Send Reminder" button (automatic email with payment link)
→ Record activity (note in customer file)
> 14 days without payment
→ Phone call + formal notification email
→ Record activity
> 30 days without payment
→ Report to Sales Manager and CFO
→ New order deliveries can be suspended until regularised
> 60 days without payment → management decision: payment plan or debt recovery
Workflow 4 — e-Invoice for B2B customer
Invoice issued for customer with valid VAT number
→ Finance → e-Invoice → "Submit to ANAF" button on invoice
OR
→ Automatic submission (if Auto-send = ON, after X days)
ANAF processes → 3 possible statuses:
├── Validated (OK) → download signed archive if needed
├── Validation error → identify incorrect field (address, VAT, tax rate) → correct invoice → resubmit
└── Duplicate → invoice was previously submitted → check existing archive
Importing supplier invoices (reverse):
→ e-Invoice → Import from e-Invoice → your suppliers' invoices from SPV enter automatically
→ Reconcile with Purchase Orders (hand to AP Accountant)
Workflow 5 — Reversal / Credit Note
Customer returns goods or requests invoice correction
→ Sales → Credit Notes → Add
→ Associate the original invoice
→ Fill in items and amounts to reverse
→ Credit Note automatically reduces customer balance
→ If credit note covers an overdue invoice → invoice is considered "partially paid"
→ If customer is entitled to refund → record the reverse payment
→ Credit Note must also be submitted to ANAF if the original invoice was sent via e-invoice
e-Invoice — what you need to know as AR Accountant
Conditions for an invoice to be eligible for e-invoicing
| Condition | What to check |
|---|---|
| Customer has valid VAT number | VAT field in customer file correctly filled in |
| Invoice is in RON | Currency = RON (e-invoice doesn't accept other currencies) |
| Invoice is not draft or cancelled | Active status |
| Your company's VAT configured | Settings → General → company_vat |
Common ANAF validation errors
| Error | Cause | Solution |
|---|---|---|
| Invalid customer VAT | Incorrect VAT or wrong format | Check VAT on anaf.ro → update in customer file |
| Missing address | Customer has no complete address | Fill in address in CRM → Clients |
| Incorrect VAT rate | Rate not recognised by ANAF | Check with General Accountant the configured rates |
| Duplicate invoice | Same invoice submitted twice | Check existing archive |
Metrics to track
| Metric | What it means | Target |
|---|---|---|
| DSO (Days Sales Outstanding) | Average days from invoicing to collection | Industry benchmark: 30–45 days B2B |
| % invoices paid on time | Invoices collected on or before due date | > 80% |
| AR value > 30 days | Higher-risk receivables | Reported weekly to CFO |
| e-invoice compliance rate | % B2B invoices successfully submitted to ANAF | 100% of eligible ones |
| Unreconciled payments | Received payments not associated to an invoice | 0 at end of day |
Practical tips
Reconcile the bank statement the same day. An unrecorded payment means the invoice continues to appear as overdue — the customer receives a reminder even though they've paid. That damages the relationship.
Check the customer's VAT number before submitting to ANAF. An incorrect VAT = validation error = invoice doesn't reach ANAF = potential fine. 30 seconds on anaf.ro saves a lot of wasted time.
Don't issue a Credit Note without knowing whether the original invoice was sent to ANAF. If it was, the credit note must also be sent to ANAF. An unregistered credit creates a discrepancy.
Document every contact with an overdue customer. A note added to the customer file with the date, person contacted, and what was agreed protects the company if you end up in dispute.
Configure Workflow Automation to send payment reminder emails automatically at 7 days before due date and 1 day after overdue — this covers 80% of collection follow-up without manual intervention, running 24/7.
Recording a payment on the wrong invoice marks the wrong invoice as paid while the actual overdue invoice continues ageing. Check payment references against bank statements carefully before confirming every payment.