Invoices & Billing: The Anatomy of One Invoice Row

One invoice row, part by part

Every card on the screen is assembled from the same eight elements. Read them in this order and you have the whole picture without opening anything.

The border colour is the piece worth internalising, because it is the only signal you can read peripherally. Scrolling a list of thirty invoices, red edges pull the eye without any reading at all. That is the correct hierarchy: the state of an invoice is more urgent information than its number.

Total or Remaining: the most important word on the card

The large figure on an unpaid invoice is what is still owed, and the small word above it tells you whether that is the same as what was billed.

• Nothing paid yet, so the balance equals the invoice value: the label reads Total.
• A part payment has been recorded: the label switches to Remaining, the figure drops to the balance, and a smaller line beneath gives the original total.
• Fully settled: the label reads Total again, because at that point the useful number is the invoice value, not a zero balance.

This matters because part payments are common in agency work — deposits, staged billing, a client paying most of something and querying one line. A portal that always showed the invoice value would be actively misleading in every one of those cases, and a portal that always showed the balance would confuse a client trying to reconcile against their own records. Showing the balance and labelling it, with the total available underneath, is the version that survives both situations.

The same logic runs into the payment action. Pay Now charges the outstanding balance, not the invoice value, so paying a part-paid invoice does not overcharge. And an invoice with nothing left to pay refuses politely: it tells you it is already paid rather than opening a checkout for nothing.

Overdue is calculated, not stored

There is no overdue flag on an invoice in Arpixa. Overdue is worked out at the moment you look at the screen, from two conditions:

1. The invoice is not Paid.
2. Its due date is in the past.

This is a better design than a stored flag for a reason worth explaining. A stored flag has to be updated by something — a scheduled job, a background task, someone opening a record. Any of those can fail or lag, and an invoice that is overdue but not yet flagged is the exact failure that erodes trust in a billing screen. Calculating it means the answer is correct every time it is asked.

The order of the two conditions also matters. Paid is checked first, so an invoice settled a fortnight after its due date is simply Paid, not Paid-and-Overdue. From a client’s point of view that is obviously right, and it is the kind of detail that separates a billing screen people trust from one they learn to ignore.

Four tabs that deliberately overlap

Four filters sit above the list, each carrying a live count: All Invoices, Unpaid, Paid, and Overdue.

Unpaid and Overdue are not mutually exclusive, and that trips people up until you see the intent. Unpaid means everything not yet settled. Overdue is the subset of Unpaid that is late. An invoice due in ten days shows in Unpaid; an invoice due ten days ago shows in both.

They are lenses, not folders. Unpaid answers “what do I owe in total”. Overdue answers “what am I in trouble for”. Both questions are real, and a client who is being chased usually wants the second one first.

Alongside the tabs sit an agency selector and a search box, and when a filter combination returns nothing the screen offers to clear all three at once rather than leaving you to work out which one was too narrow.

Paying, and the gateway question

Pay Now appears on any invoice with a balance remaining. What happens next depends on the agency that raised it, because payment options are configured per agency, not globally.

Arpixa supports two gateways, Stripe and Razorpay, and an agency can also attach a payment link to an invoice instead. A client working with an agency in one country and an agency in another may therefore pay each of them through a different rail from the same screen, which is exactly what should happen and is invisible in practice.

Checkout is for the outstanding balance. Once payment completes, the portal confirms it and the receipt becomes available immediately rather than after a reconciliation delay. The agency-side view of the same rails, including how payment records are matched back to invoices, is in Payments.

Billing clients through the portal is not an add-on. The four Arpixa tiers cost nothing, $12, $29, and $89 a month, and what they change is client capacity. Gateway availability and current limits are on the pricing page.

When an agency has not set payments up

If an invoice has no gateway available and no payment link, the card shows an amber warning in place of a working payment path.

This is worth calling out because it is a rare piece of honesty. The easy option would be to render a Pay Now button that fails on click, or to hide the invoice, or to say nothing. Instead the client is told directly that there is no way to pay it here, which sends them to the right conversation instead of a support ticket.

For agencies, that amber box is a prompt worth acting on. An invoice a client can see but cannot pay is the worst of both worlds: you have created the expectation of self-service and then not delivered it. The case for closing that gap is made in payment links for agencies.

What changes once it is paid

A settled invoice does not disappear. It changes character in four small ways.

• The border goes neutral grey and the invoice number greys out, so paid work recedes without vanishing.
• The badge becomes Paid, and the calculated overdue state stops applying entirely.
• The action area replaces Pay Now with a payment-complete confirmation.
• View and download become receipt actions, producing a document marked as paid rather than a copy of an outstanding bill.

That last distinction is the one an accounts department cares about. A PDF of an invoice and a PDF of a receipt are different documents with different purposes, and most portals hand you the first one and call it the second. Arpixa keeps every invoice permanently, so the receipt for something paid two years ago is still one click away.

Several agencies, one billing screen

For a client with more than one connection, this screen is a merged billing view. Every invoice from every agency is in the same list, with the agency identified on each card and an agency selector to narrow it.

That is more useful than it first appears. A client who works with three suppliers normally has their agency spend spread across three portals and an inbox, and answering “what am I currently committed to” means opening all of them. Here the Unpaid tab answers it in one number.

If what you want is the trend rather than the list — total spent, outstanding, next due, spend per agency — that is a different screen. My Payments aggregates the same data as metrics; Invoices is the document-level view. And due dates from this screen also appear on the Calendar, with the amount and status attached.

How to pay an invoice

1. Open Invoices in the portal and switch to the Unpaid tab.
2. Check the amount label on the invoice you intend to settle: Remaining means part of it is already covered.
3. Open View Invoice first if you want to check the line items before paying.
4. Choose Pay Now, which starts a checkout for the outstanding balance rather than the full total.
5. Complete payment with whichever gateway that agency has enabled.
6. Return to the list and confirm the card has flipped to Paid, then download the receipt.

Step two is the one worth building a habit around. Checking whether the label says Total or Remaining takes a second and is the only way to know whether the number in front of you is the whole bill or the rest of it.

Frequently asked questions