# Sage X3 Error: Due Date Is Being Paid, and How to Clear It > Source: https://netray.co/erp-help/sage-x3-error-due-date-being-paid > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer This Sage X3 message means the due date (the open item on a supplier or customer invoice) is already attached to another payment, payment proposal or lock that has not finished, so a second payment cannot take it. Find the unposted payment, proposal or user session holding the due date, post or delete it, then retry. Exact wording varies by X3 version and folder, so match the mechanism rather than the text. ## Kind error ## System sage ## Erp Sage X3 ## Module Accounts Payable / Payments ## Query sage x3 error due date being paid ## Alternate Queries - error message sage x3 - sage x3 due date already in payment - sage x3 payment proposal due date locked ## Applies To Sage X3 V7, V11 and V12 (Syracuse web client), supplier and customer payment entry and payment proposals ## Steps ### How to find and release the due date **Items:** - Note the invoice number, supplier or customer code and due date line named in the message. The error is about one open item, not the whole invoice. - Open the payment entry function for that third party (Accounting, Payments, Payment entry) and look for an unposted or in-progress payment that includes that invoice. Filter by status and by user. - Check payment proposals and payment runs (the proposal and automatic payment functions under Accounting). A proposal that was validated but not posted keeps its due dates reserved. - If the payment is yours and incomplete, either finish and post it or delete the draft so the due date returns to open. - If another user owns it, ask them to close the screen. An abandoned browser tab can leave a record lock until the session times out. - If a lock persists with nobody working on it, ask an administrator to clear it from the lock and user session administration, never from the database directly. - Retry the payment. Confirm in the open items inquiry that the due date shows the expected remaining balance. ## Sections ### What the message actually protects **Body:** In Sage X3 an invoice produces one or more due dates, each an open item with an amount and a payment status. When a payment, a proposal or a settlement picks up that due date, X3 marks it as in use so two documents cannot both settle the same money. The message is the system preventing a double payment. That is why it is mostly a symptom of workflow, not corruption. The due date is tied to a document that exists but is not finished, either because someone is still building it, because it was validated but not posted, or because the session that held it ended abnormally. ### The three usual causes **Body:** First, a payment proposal or automatic payment run that was generated but never posted. Proposals are batch objects, so the person who runs them may not be the person now trying to pay one invoice manually. Second, a manual payment entry saved as incomplete or left open in another tab. Third, an interrupted Syracuse or batch server session that left a lock behind. Distinguish them by status. If a document exists with the invoice on it, it is cause one or two and you resolve it in that document. If no document exists but the error persists, suspect a stale lock and involve your X3 administrator. ### Safe ways to resolve it and what to avoid **Body:** Prefer completing or cancelling the owning document. That keeps the audit trail clean and releases the due date through normal logic. Posted payments should be reversed through the supported payment cancellation, not edited. Avoid updating payment tables by SQL to flip flags. It can leave the due date, the journal and the bank file out of step, and it is hard to reconcile at period end. If a script is truly needed, test it in a copy folder first and have finance sign off. **Code:** -- Read-only diagnostic idea (table names differ by folder; verify first): -- find open payment documents that reference the supplier and invoice -- using the payment header and line tables in your X3 data dictionary ## Pitfalls - Deleting the invoice or its due date to make the error go away. That breaks the ledger link. - Assuming another user caused it when the cause is a validated but unposted proposal from last week. - Clearing locks while a payment run is genuinely processing, which can corrupt a bank file batch. - Editing database flags directly instead of using the X3 cancel or delete functions. - Retrying the same payment repeatedly instead of finding the owning document. ## Ai Angle An AI assistant grounded in your X3 data, such as ERPray read-only, can answer which payment, proposal or user currently holds a given invoice due date, and show the query it ran. That turns a hunt across screens into one question. Release and cancel actions stay with a person under normal X3 roles. ## Faq ### Is the due date being paid error a bug? **Answer:** Usually not. It is X3 preventing the same open item being settled twice. The cause is normally an unfinished payment, a validated proposal that was never posted, or a stale lock from an interrupted session. Fix the owning document and the error clears. ### How do I find which payment holds the due date? **Answer:** Search payment entries and payment proposals for the supplier or customer and invoice, filtering by status that is not posted. If nothing is found, check the open items inquiry for the due date and ask an administrator to review locks. ### Can I just reset the due date in the database? **Answer:** It is possible but risky. The due date, journal entries, bank file and audit trail must stay consistent. Use the supported cancel or delete function, and only script changes in a test copy with finance approval. ### Does this apply to customer receipts too? **Answer:** The same locking principle applies to customer due dates in receipt entries and collection runs. The functions are different but the fix is the same: find the unfinished document or lock that holds the due date, finish or remove it, then retry. ## Search terms sage x3 error due date being paid, sage x3 payment error, sage x3 payment proposal locked, sage x3 due date locked, error message sage x3, sage x3 accounts payable, sage x3 open items, sage x3 duplicate payment --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json