Перейти к содержимому

Voiding an invoice

Это содержимое пока не доступно на вашем языке.

Voiding is the escape hatch for a wrong invoice. Unlike a Credit Note (which records a corrective adjustment), voiding erases the invoice’s effect entirely.

Open the invoice → click Void invoice → enter a reason → confirm. The platform runs the following inside a single database transaction:

  1. Reverse the GL posts. Every row tagged with sourceType = 'invoice' and sourceId = <this invoice> is mirrored with opposite Dr/Cr. Net effect: zero.
  2. Reset linked cars to purchased. Each car line’s status flips from sold_* back to purchased. The container/RORO assignment stays intact — you can re-issue without losing shipping context.
  3. Restore customer deposits. If the original invoice cleared X from 2100, voiding posts X back to 2100, tagged to the same buyer.
  4. Reverse FX-realized rows. If payment had been recorded and cross-currency FX was realized, those gains/losses unwind.
  5. Reverse vault cost-basis impact. If payment was settled in a foreign vault, the vault’s homeBalanceAtCost is mirrored back.
  • Always when the invoice is still in draft status (no harm done).
  • Even when fully or partially paid — payment reversal cascades.
  • NOT when the invoice’s period is locked (see Trial balance & reports).
  • The PDF you already emailed the buyer.
  • Time. Pre-existing aged reports run before the void will still show the AR.

After voiding, the cars are back in purchased status with their full inventory cost intact. You can immediately re-add them to a new invoice with corrected details. Common pattern: void the typo’d invoice → re-create with the right numbers → issue → resend PDF.