Posting statuses
Every status a payment posting can reach in Drypowder, and what each one means.
This page documents the statuses that appear on a payment posting in Drypowder. Understanding these lets an AR operator know whether a posting is in progress, finished, or needs attention.
Posting-level statuses
These statuses describe the overall posting batch — the settlement or group of payments that an operator submits at once.
| Status | Meaning |
|---|---|
| Created | The posting job has been created and is waiting to be picked up for processing. |
| Posting | Drypowder is actively sending payments to Spruce. The posting is in flight. |
| Completed | All payments in the batch posted successfully. Nothing requires follow-up. |
| Partially completed | Some payments posted and some failed. The payments that failed need to be reviewed. See Resolve a posting error. |
| Failed | The posting failed before any payments were sent to Spruce, typically due to a connection or configuration error. |
| Failed validation | Drypowder rejected the batch before sending it, because the posting file did not pass internal checks. |
Request-level statuses
Each payment inside a batch has its own status. These are visible when you drill into a posting.
| Status | Meaning |
|---|---|
| Pending | The payment is queued and has not been sent to Spruce yet. |
| Pre-verification | Drypowder is verifying balances in Spruce before posting. The invoices in this payment are checked against what Spruce currently shows. |
| Posting | The payment is being submitted to Spruce right now. |
| Posted | Drypowder sent the payment to Spruce. Waiting for Spruce to confirm it accepted. |
| Polling | Drypowder is checking Spruce to confirm the posting registered. This step handles the delay between submission and confirmation in the Spruce API. |
| Polling complete | Spruce confirmed the posting. Drypowder is now running a final balance check. |
| Post-verification | Drypowder is verifying that the balances in Spruce dropped by the expected amounts after posting. |
| Completed | The payment posted and the balances verified correctly. This payment is done. |
| Failed | The payment failed at some point in the process. The error detail explains why. See Resolve a posting error. |
Why posting has multiple steps
Drypowder does not simply fire a request at Spruce and assume it worked. Each payment goes through a pre-verification check, a posting step, a confirmation poll, and a post-verification check. This sequence catches mismatches — for example, a customer who paid an invoice through another channel between the time the payment was submitted in Drypowder and the time it reaches Spruce.
When a payment stops at Failed in any of these steps, the error details tell you where in the sequence it stopped and why.
Related
- Resolve a posting error — What to do when a posting fails.
- How payments post to the general ledger — What happens inside Spruce once a payment posts.
- Reconcile and post settlements — Running the posting workflow.