Skip down to the research record

Standalone payment against an invoice: 3 dates to track

Quota Forecast Editorial Team · Published · 13 min read

A standalone payment is money a customer has paid that is not yet matched to an invoice. When a quarter closes with an invoice still showing an open balance, the question that comes back is usually simple: where did the money go? Often the answer is a payment that arrived, sat without being tied to any invoice, and was later applied or taken off again. Applying it reduces the open balance. Unapplying it puts the balance back. Each of those steps changed what the open balance looked like on the day someone pulled the report.

This post follows one case from start to finish. Stripe's documentation on revenue recognition for subscriptions and invoicing describes a standalone payment and an invoice with exact dates and amounts, which makes it a clean teaching example. Every date and amount below comes from that example. Three dates do most of the work: the day the payment arrives, the day it is applied to the invoice, and the day it is unapplied. If you can state those dates and the amount on each, you can explain most questions about an open balance without rebuilding the whole set of books.

This is a way to organize the evidence, not a set of accounting rules for your company. Your accounting policy, your billing system, and your auditors decide how your books work. What follows helps you ask them the right questions.

The example we will follow

The case has one customer, one payment, and one invoice. The customer makes a standalone payment of 20 USD on January 10, and that payment is not yet attached to any invoice. On January 15, an invoice for 31 USD is created and finalized. The invoice covers a service period from January 15 to February 14, and the total due amount on the generated invoice is 31 USD. The Stripe documentation lays out these steps in order.

Put plainly, the company holds cash from the customer, and the customer has an invoice open. Those two facts stay separate until someone attaches the payment to the invoice. That link, and the timing of it, is the whole subject of this post.

Write the example down before you start. A simple sheet with the customer, the payment amount, the invoice amount, and the three dates is enough. Every later check in this post is a question you can answer by looking at that sheet and at your own system's records.

January 10: the payment arrives unattached

On January 10, the company receives a standalone payment of 20 USD that is not yet attached to any invoice, according to the Stripe documentation. At that moment the invoice does not exist. It is created and finalized five days later, on January 15, for 31 USD.

That gap matters more than it looks. The payment is real money, but on January 10 it reduces nothing on any invoice. If your report counts open invoices, an unattached payment may not appear against any of them. If your report counts cash received, it does. Before you answer why an invoice is still open, find out which view the number came from. Two reports can both be right and still disagree, because one is built from cash received and the other from invoices.

This is also where the credibility question starts. When a board member or an auditor sees a deposit from a customer next to an invoice that still reads as open, the first reaction is often that something is wrong. Nothing has to be wrong. The deposit and the invoice are two records, and the January 10 entry is only the first of them. Saying that plainly, with the date attached, usually settles the matter faster than any argument about the systems.

The invoice's service period adds a second wrinkle. The service period runs from January 15 to February 14, so it spans two calendar months. The invoice date, the service period, and the payment date do not line up neatly, and a month-end cutoff can fall in the middle of them. When you explain the balance, name the date you are using. Switching between the payment date, the invoice date, and the service period in one conversation is one of the easiest ways to make a correct number look wrong.

On the day the invoice is finalized, nothing has been applied yet. The invoice carries its full 31 USD as open, and the 20 USD payment is still sitting unattached. Money arriving does not change the invoice. Only an application does, and that is the next date.

A useful habit is to write each event as a one-line log entry. For this example, the first two lines read: January 10, payment of 20 USD received and not attached to any invoice; January 15, invoice for 31 USD created and finalized, service period January 15 to February 14, nothing applied. Those two lines explain why the invoice looked fully open on any report pulled from January 15 up to February 1.

February 1: the payment is applied

On February 1, you apply the 20 USD payment to the invoice, following the Stripe documentation. This is the date the open balance changes. The payment moves from sitting on account to reducing the 31 USD invoice, so the open amount falls by 20 USD. The rest of the invoice stays open after this step.

Receiving and applying are separate events, and that is the first thing to get straight. The money arrived on January 10 and reduced the invoice on February 1, three weeks later in this example. Someone who compares the January 10 deposit with the February 1 balance may think the numbers disagree. They don't. They are recorded on different dates, and the report has to say which date it reflects.

The application date also decides which reports show the reduction. If your quarter-end cutoff falls before February 1, the invoice still carries the full open amount at that cutoff, even though the payment arrived earlier. If the cutoff falls on or after February 1 and the application is recorded by then, the reduction is part of the closing balance. The same payment can appear as an open balance in one report and as a reduction in another, purely because of when it was applied.

That is why the application date needs to be exact. Date it to the day the match happened, not the day someone got around to entering it. A late entry dated back can make a cutoff report look different from the one pulled at the time. If your system lets you backdate, ask who has that permission and whether backdated entries are flagged anywhere.

Ask, too, what the application was matched against. The example has one payment and one invoice, so the match is simple. In a busier account, one payment might be spread across several invoices, or several payments might cover one invoice. A single date on a single line can hide that, so when you see a February 1 application, confirm the amount and the invoice it touched.

March 5: the payment is unapplied

On March 5, you unapply the 20 USD payment from the invoice, a step the Stripe documentation also records. The payment detaches, and the open balance goes back up. The example records the step but not the reason. In a real team, reasons vary: a payment matched to the wrong invoice, a customer dispute, a refund conversation, or a correction made during review. Don't assume a reason just because the step is recorded. Ask the person who made the change, and write down the answer.

This date tends to surprise people. It is easy to expect an open balance to fall as customers pay and never rise again. This example shows that it can rise. A report pulled between February 1 and March 4 shows the payment applied. A report pulled on or after March 5 shows it unapplied and the invoice open again. Both can be correct for the date they were pulled. A balance is a point-in-time fact, and the three dates let you say which point you mean.

From the payment's point of view, the state after March 5 matches January 10: money received, not attached to any invoice. From the invoice's point of view, it matches January 15: open, with nothing applied. The record has come back to where it started, but the history between those dates still happened, and a quarter-end report may have captured one of the middle states.

So a reader who saw only the January 10 and February 1 records would give a stale answer. If February 1 was the last record you checked, the balance you quote may already be out of date. The March 5 entry changes the story most, so check it first when a number seems to have moved for no clear reason.

Reading the three dates against a quarter-end

Quarter-end questions are rarely about today's balance. They are about the balance at a cutoff, a specific day someone chose in advance. Set the cutoff first, then use the three dates to decide what the invoice and the payment looked like on that day.

The example gives five states, and the cutoff decides which one applies:

Cutoff fallsPayment statusInvoice statusOpen amount on the invoice
Before January 10Not yet receivedNot createdNone yet
January 10 up to January 15Received, not attachedNot yet createdNone yet
January 15 up to February 1Received, not appliedCreated and finalized for 31 USD31 USD
February 1 up to March 5Applied to the invoiceOpen, partly reduced31 USD less the 20 USD applied
March 5 or laterUnapplied, not attachedOpen again31 USD

Each row is a different answer to the same question, and the same three dates support all of them. The skill is in knowing which state your cutoff lands in and saying it out loud. A reader who hears "the payment was applied" will assume it was applied at the cutoff, so say directly whether the application was still in place on that date.

A practical test helps. Pick one invoice that moved during the quarter and walk it through each row. If you can explain every state without looking anything up, your team can answer the quarter-end question too.

Set the cutoff to the day your quarter closes, not the day you happen to read the report. A report pulled after the quarter ends, for a cutoff on its last day, can show a different balance than the one the close team used, and the difference can come down to one date entry. The example's dates are not your dates. Replace them with your own cutoff and records, and run the same checks against each state. For more on cutoff dates, see quarter cutoff dates.

Pulling the three dates from your own system

The example is clean. Real records are less tidy, and the screen you open may show only the current state. If you open the invoice later, it shows what is true then. A March 5 unapplication may have overwritten the February 1 application in the view. A current-state view answers what is open today, not what was open at the cutoff. For a quarter-end question, you need history.

Filters can hide the same problem. HubSpot's guide to setting a fiscal year gives one example of a date filter: "In the right panel, in the is dropdown menu, select This fiscal quarter so far." The useful lesson is not the menu itself. A filter defines the window you are looking at, so before you trust a report, check which window it covers and whether your cutoff falls inside it.

So ask your billing or finance team for four things. First, the date the money landed, from the bank or payment processor. Second, the date the payment was attached to the invoice. Third, the date it was detached, if it ever was. Fourth, the date the invoice was finalized. Those four dates are the three dates plus the finalization date. If any of them is missing, say so in your explanation rather than filling the gap with a guess.

Look for an audit trail or change history on both the payment and the invoice. Many systems keep one, though the detail varies, so confirm what yours records before relying on it. If history is not available, export the payment-to-invoice links at each quarter-end cutoff and keep the export with the close file. The next person who asks won't have to rebuild the history from memory.

Check the amounts as carefully as the dates. The example has one payment of 20 USD matched to one invoice of 31 USD. Real accounts often have several payments, partial applications, and credits. A partial application changes the arithmetic, and a single date does not capture that. Record the amount applied on each date along with the date, so the open balance you quote can be rebuilt from the records. For how the amounts reconcile to invoice totals, see invoice extract reconciliation.

Finally, decide who owns the history. Revenue operations, the billing team, and the controller may each hold a piece of it. Agree before the quarter closes on who will produce the four dates on request. A question that arrives mid-close is far easier to answer when the owner already knows the question is theirs.

Explaining the number to the people who ask

Revenue leaders usually hear three questions when an open balance looks odd. The first is "why is this invoice still open when the customer paid?" Often the answer is a date gap: the payment arrived, but it was not applied at the cutoff. In the example, that is the stretch from January 10 to February 1. Think of the February 1 application as the moment the invoice starts telling the same story as the bank. Until then, the two records disagree in a predictable way, and the disagreement is about timing, not error.

The second question is "why did the balance go up after it went down?" The answer is an unapplication. Here the payment was applied on February 1 and unapplied on March 5, so the open balance rose again. Say so plainly. A rising balance is not automatically an error, and it is not automatically a sign of a bad customer. It records an event someone chose to make, or needed to correct.

The third question is "the bank shows money from this customer, so why doesn't the invoice reflect it?" The answer depends on the report. A cash view shows the deposit on its date. An invoice view shows it only once it is applied. Both can be right, and the explanation should name the view before it names the number.

A short explanation you can adapt looks like this: "At our cutoff of [date], invoice [number] shows an open balance of [amount]. The customer paid [amount] on [date]. That payment was applied on [date] and unapplied on [date], so at the cutoff it was [attached or not attached]. [Reason for the unapplication, if confirmed.]" Fill each bracket from your records, and leave the reason blank if nobody has confirmed it. A confirmed fact is worth more than a confident guess, and a blank is easier to defend than an invented reason.

If you forecast the quarter, treat applied and unapplied states as separate paths rather than assuming the balance only moves one way. Microsoft's guidance on Excel forecasting makes the general point: "A forecast can help you predict things like future sales, inventory requirements, or consumer trends." A forecast that assumes every applied payment stays applied will miss the kind of reversal shown on March 5. Build the reversal into the scenario, even if it seems unlikely, so the forecast doesn't surprise you at close.

When the close meeting asks about a balance, open with the cutoff, then the state, then the dates. That order keeps the conversation on the number rather than on who made which change.

Closing the loop

Three dates and one amount explain most of what happens to a standalone payment against an invoice: when the money arrived, when it was applied, and when it was taken off again. Write them down while the quarter is still open. Writing them after the question arrives is harder, and the history may already be out of reach.

Sources