Every payment milestone on a project carries a small status badge that tells you where that payment stands — from “still waiting on the client” to “money’s in.” Most of the time it’s self-explanatory, but one status in particular trips people up: Payment Processing. This article walks through each status, what actually triggers it, and clears up the most common point of confusion.
If you haven’t set up your payment schedule yet, start with Setting Up Your Payment Schedule. This article picks up after the schedule exists and invoices start moving.
The Statuses at a Glance
A milestone moves through a simple lifecycle. You’ll see one of these badges on it:
No badge yet — the milestone is on the schedule but you haven’t billed it. Nothing has been requested from the client, so there’s nothing to track yet.
Payment Required — you’ve sent the payment request and you’re waiting on the client. The amount is due; the ball’s in their court. (On a milestone you’ve marked as non-payable, you’ll see Pending Approval here instead, since there’s no dollar amount to collect.)
Payment Processing — a payment has been started or recorded against this milestone, but it hasn’t been confirmed as received yet. This is the one worth understanding well — more on it below.
Complete — the payment is confirmed and the milestone is settled. This is the finish line.
A Closer Look at “Payment Processing”
The single most important thing to know: Payment Processing does not mean the money is in your account. It means a payment is in motion and waiting on a final confirmation. There are two everyday situations that land a milestone here.
1. The client paid online and it’s clearing. When a client pays by bank transfer (ACH) or card through Eano, the funds take a little time to settle. During that window, the milestone sits in Payment Processing — the payment is real and on its way, it just hasn’t fully landed.
2. The client is paying offline (check or Zelle). When a client chooses to pay by check or Zelle, they let you know through Eano that the payment is on the way. The milestone moves to Payment Processing to reflect “this one’s been arranged” — and it stays there until you confirm the money actually arrived. This is the key difference from an online payment: with an offline method, nothing has been charged or transferred through Eano. Processing simply means it’s been recorded and is awaiting your confirmation.
So a milestone in Payment Processing is best read as: “A payment has been recorded here, but it’s not done until it’s confirmed received.”
How a Milestone Moves From One Status to the Next
Getting to Payment Processing happens one of two ways: - The client opens the payment request and pays online, or tells you they’ve sent an offline payment (check or Zelle). - You record a payment against the milestone yourself using Mark as Paid — for example, when a client hands you a check directly or pays in cash. You’ll enter the amount, date, and payment method.
Getting to Complete is the confirmation step: - For an offline payment that’s sitting in Processing, open the milestone and use Mark as received once the funds are actually in hand. That’s what moves it to Complete. - Online payments move to Complete on their own once the funds finish settling.
There’s no separate “mark this milestone done” step beyond the payment itself — recording and confirming the payment is what advances the milestone.
When a Number Looks Off
A few situations trip people up more than any status badge does. All of them are quick to sort out once you know where to look.
You recorded a payment with the wrong details. Say a client told you they’d pay cash, so you recorded it that way, and then they handed you a check instead. Or you fat-fingered the date or the amount. You don’t need to start over. On the Finance tab under Income, click the arrow at the left of the row to show its payments, then click the payment (or use its ••• menu) and choose Edit. You can change the amount, Payment Date, Payment Method, Reference, Payment Memo, and attachments. Save, and the totals and status recalculate. If the payment shouldn’t be there at all, choose Delete instead.
A couple of limits: the amount can’t go above what’s owed on the request, and payments your client made online by card or bank transfer can’t be edited or deleted, since they match what actually moved through the payment processor.
When your client pays a different amount than you asked for. This is the common one, and it’s not a problem at all. Say you requested $6,150 and the client sent a check for $6,000. Click Mark as paid and record the $6,000. That’s what actually happened, and the record should reflect it. The milestone keeps its Request sent status, the Received column shows $6,000, and your client’s portal shows the $150 that’s left. If they pay online, they’re only asked for that $150.
When the rest comes in, click Add payment on the same row and record it. Once the payments add up to the full request, the milestone switches to Paid on its own, so a short payment can’t quietly slip past you. For the full walkthrough, see When Your Client Pays Part of an Invoice. If you’d rather bill a milestone in planned pieces from the start, see Billing Partial Progress Against a Milestone.
If a client overpays through progress payments, the summary across the top of the milestone (Total, Pending, Paid, Remaining) shows Remaining as a negative figure marked (overpaid), so it’s visible rather than silently absorbed.
One thing you can still catch in time: if you sent a progress payment request for the wrong amount and the client hasn’t paid it yet, the entry sits at Requested and carries a Cancel link. Cancel it and send a fresh request for the right figure. Once the client has paid, that option is gone and record what the client actually paid, as above.
A tiny balance won’t clear. Every so often a project shows a stubborn few-cents balance due — like $0.96 — even though you and the client both know it’s paid in full. Almost always this means your payment schedule doesn’t add up to your contract total: the milestone amounts sum to a hair less than the full price, usually a rounding leftover from when the schedule was built in percentages. Eano reports that gap as an outstanding balance. To clear it, true up the milestone that’s short from the Payment Milestones tab so your milestones add up to the exact total. Once what was billed and what was collected line up, the balance falls to zero. If you can’t adjust the figure — milestone amounts firm up as a project gets underway — reach out and we’ll help you square it.
The Send Button Is Gone — and That Usually Means It Already Sent
A common moment of panic: you open a milestone to request payment, and the Confirm & Send Invoice button isn’t there. Nothing is greyed out with an explanation — the button is simply absent, which reads like something is broken.
It almost never is. That button only appears while a milestone is still at Not started — meaning no payment request has gone out yet. The moment you send one, the milestone flips to Payment Required and the milestone view switches to a read-only summary of the request you already sent. The send button disappears because there is nothing left to send.
So before assuming it’s a glitch, look at the status badge on the milestone itself:
Not started — nothing sent yet. The Confirm & Send Invoice button should be right there.
Payment Required — you already sent it. Your client has the request; you’re waiting on them. Nothing more to do from your side except follow up, or Mark as Paid once the money lands.
Payment Processing — a payment is in flight. Wait for it to settle, or use Mark as received for an offline payment.
Complete — paid and closed out.
This catches people most often on a freshly signed contract, because the first billable milestone can send its payment request automatically right after signing — look for the blue Automatic send enabled badge on it. If that’s switched on, your client already has the first request before you ever open the milestone, and the button was never going to be there.
If you genuinely need the client to receive the request again — they deleted the email, say — you don’t re-send from the milestone. Share the invoice link with them directly, or nudge them from the project.
A Few Things Worth Knowing
Processing isn’t a guarantee of collected funds. Because an offline payment can be recorded before the check clears, don’t treat Payment Processing as money in the bank. Wait until it’s Complete (or until you’ve confirmed receipt) before counting it.
The Progress bar reflects this. A milestone in Payment Processing counts toward the project’s Progress bar (it’s “underway”), but the Paid figure in the Revenue column only counts money actually received. That’s why a project can show progress while Paid still reads lower — see Understanding Project Progress for the full picture.
If a status doesn’t look right, check the milestone first. Open the milestone to see what payment was recorded against it and how. If a milestone is showing Payment Processing and you’re not sure why, it usually means a payment was recorded or arranged and is waiting to be confirmed as received. If it still doesn’t add up, reach out to us and we’ll help you sort it out.
Frequently Asked Questions
I can’t click “Confirm & Send Invoice” — the button is missing or won’t respond. What’s wrong? Check the milestone’s status badge first. If it reads Payment Required, the request has already been sent and the button is intentionally gone — the milestone switches to a read-only view of the request that went out. This is the most common cause by far, and it’s especially easy to miss on a newly signed contract, where the first billable milestone can send its request automatically.
My client got a payment request I don’t remember sending. That’s the automatic first payment request. When a contract is signed, Eano can send the request for the first billable milestone on its own — the milestone will carry a blue Automatic send enabled badge. It’s a per-project setting, so turning it off on one job doesn’t change the next one.
Does “Payment Processing” mean I’ve been paid? Not necessarily. It means a payment has been recorded or started against the milestone but isn’t yet confirmed as received. For online payments it’s the settling window; for offline payments (check or Zelle) it’s a placeholder until you confirm the funds arrived. Wait for Complete before treating it as collected.
A milestone is in Payment Processing but my client says they haven’t paid through Eano. What happened? That’s normal for offline payments. If a check or Zelle payment was arranged — or recorded on the account as expected — the milestone sits in Payment Processing until it’s confirmed received, even though no money moved through Eano itself. If you don’t recognize the entry at all, reach out to us and we’ll take a look with you.
How do I move a milestone from Payment Processing to Complete? Open the milestone and use Mark as received once the payment is actually in hand. Online payments will complete on their own as the funds settle.
What’s the difference between “Payment Required” and “Pending Approval”? Both show on a milestone that hasn’t been paid. Payment Required appears on a milestone with a dollar amount that’s been billed. Pending Approval appears on a milestone you’ve marked as non-payable — it’s a progress checkpoint, not a payment, so there’s nothing to collect.
I recorded a payment with the wrong method, date, or amount. How do I fix it? Edit it. Under Finance > Income, click the arrow at the left of the row to show its payments, then click the payment (or its ••• menu) and choose Edit. Change whatever’s off and save.
Why can’t I edit a payment? Usually because your client paid it online, by card or bank transfer through Eano. Those payments can’t be edited or deleted, because they match what moved through the payment processor. Payments you recorded yourself can always be edited, as long as the amount doesn’t go above what’s owed.
Can my client choose to pay only part of an invoice? Not online. When your client pays through their portal, they pay the amount on the request — there’s no box for them to enter a smaller figure. If you want to collect a job in pieces, bill each piece as its own request with progress payments; see Billing Partial Progress Against a Milestone. A client who pays you less directly — a smaller check, say — is a different situation, covered next.
My client paid less than I requested. Do I have to correct the request? No. Record what they actually paid with Mark as paid. The milestone stays open, your client sees the balance that’s left, and you click Add payment when the rest arrives. Once the payments cover the full request, the milestone switches to Paid on its own. See When Your Client Pays Part of an Invoice.
I sent a progress payment request for the wrong amount. Can I take it back? Yes, as long as the client hasn’t paid it. While the entry still reads Requested, it carries a Cancel link on the milestone — cancel it and send a fresh request for the right figure. Once it’s paid, cancelling is no longer an option, and the difference is handled as a remaining balance instead.
My project shows a small balance due — a few cents — but everything’s paid. What’s going on? That almost always means your milestone amounts don’t quite add up to the full contract total: a rounding gap of a few cents left over from a percentage-based schedule. Eano reports the difference as outstanding. Open the milestone that’s a little short from the Payment Milestones tab and adjust its amount so the schedule sums to the exact total — the balance will clear to zero. If the amount won’t budge, reach out and we’ll square it with you.
Do these statuses control the client portal? Yes — your client sees the same status on their end, so keeping milestones current (especially confirming offline payments as received) keeps everyone on the same page.