Troubleshooting
An invoice or pay statement will not save
Symptom: the app refuses an action on an invoice or a pay statement, with a message about its current status.
Both invoices and pay statements follow a fixed path, and each step will only accept certain actions. Every message below is the app protecting a financial record from being changed underneath someone. Find yours in the table.
Invoices
| Message | Why | What to do |
|---|---|---|
| "Load has no rate — cannot invoice" | Nothing to bill. | Put the agreed rate on the load. |
| "Load already has invoice … Void it first if you need to reissue" | A load can carry one live invoice at a time. | Open the existing invoice. If it is wrong, void it and create a new one. |
| "Factoring company not found in this tenant" | The factor is not set up on this account. | Add it under factoring companies, or leave the invoice unfactored. |
| "Cannot submit a … invoice — only DRAFT invoices can be submitted" | It has already been submitted. | Check the status; you may be looking for record advance or record payment. |
| "Cannot record an advance on a non-factored invoice" | Advances only exist for factored invoices. | Attach a factoring company, or record a payment instead. |
| "Can only advance a SUBMITTED invoice" | Advances come after submission. | Submit it first. |
| "Submit the invoice before recording payment" | Same reason. | Submit it first. |
| "Cannot record payment on a voided invoice" | The invoice is cancelled. | Issue a fresh invoice. |
| "Invoice already …" | The action has already been applied. | Refresh — someone else may have done it. |
| "Cannot void a PAID invoice — issue a credit instead" | Paid records are not rewritten. | Issue a credit. |
The order that always works
Draft → Submit → (Advance, if factored) → Record payment.
Voiding is available up until the invoice is paid or closed, and it walks the load back out of "invoiced" so it returns to your ready-to-invoice list.
Driver pay statements
| Message | Why | What to do |
|---|---|---|
| "A … statement already exists for this driver and week" | One statement per driver per week, once it is past draft. | Open the existing one. Void it if it needs redoing. |
| "Cannot modify a … statement — only DRAFT statements are mutable" | Lines can only change while it is a draft. | Void and regenerate, or correct on the next statement. |
| "Can only mark FINALIZED statements as paid" | Payment comes after finalizing. | Finalize it first. |
| "Cannot void a PAID statement — issue a correction instead" | A settlement the driver was paid on is never rewritten. | Add a correcting line to the next statement. |
| "Driver not found" / "Load not in this tenant" | Deleted record, or the wrong account. | Check the account switcher in the top bar. |
The order that always works
Generate (draft) → add lines → Finalize → Mark paid.
Dispatcher pay
| Message | Why |
|---|---|
| "Only the carrier owner can mark dispatcher pay as paid" | It is owner-only, deliberately. |
| "Already marked paid" | Someone got there first. Refresh. |
Nothing accrued on a delivered load
Check, in order:
- Settings → Dispatcher pay amount is above zero. Zero turns it off.
- The load actually reached Delivered.
- There is a dispatcher on the account for the payment to belong to.
Dispatcher pay never blocks a delivery. If it cannot work out who to pay, the delivery still completes and no payment is written.
When to contact support
Send the invoice or statement number, the exact message, and what you were trying to do. These messages are precise, so quoting one usually resolves it immediately.
Related
Still stuck?
Email support@dynamanic.io with your company name, what you did, what happened — quoting any message on screen — and when, with your timezone.