Sage X3 Error: Due Date Is Being Paid, and How to Clear It
sage x3 error due date being paid
Also searched as
- error message sage x3
- sage x3 due date already in payment
- sage x3 payment proposal due date locked
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.
Applies to: Sage X3 V7, V11 and V12 (Syracuse web client), supplier and customer payment entry and payment proposals
How to find and release the due date
- 1Note 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.
- 2Open 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.
- 3Check 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.
- 4If the payment is yours and incomplete, either finish and post it or delete the draft so the due date returns to open.
- 5If another user owns it, ask them to close the screen. An abandoned browser tab can leave a record lock until the session times out.
- 6If 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.
- 7Retry the payment. Confirm in the open items inquiry that the due date shows the expected remaining balance.
What the message actually protects
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
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
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.
-- 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
Try it here, free
Sage X3 Import Template Worksheet
An editable import tracker for Sage X3: which object, which import template, source file, records loaded, errors and owner, with error rates calculated.
Common 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.
How an ERP-grounded AI assistant handles this
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.
Frequently asked questions
Is the due date being paid error a bug?
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?
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?
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?
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.
Related
Sage X3 REST API: Reading Sales Orders Through Syracuse
Sage X3 (version 7 and later) exposes data through Syracuse at a URL of the form /api1/x3/erp/ENDPOINT/REPRESENTATION, where the endpoint is the folder and the representation is a published object such as SORDER. A GET with credentials returns JSON, and you filter with a where clause and page with count and a link to the next page. Your integration user needs the right Syracuse and X3 rights for that representation.
Error fixSage X3 Syracuse Service Won't Start: Troubleshooting Guide
When Sage X3 users reach no login page, check the Syracuse Windows service and its dependencies in order: the MongoDB service that holds Syracuse configuration, the port and certificate Syracuse binds to, then the connection from Syracuse to the X3 runtime. Syracuse log files normally state which step failed, so read the log before restarting things repeatedly.
How-toHow to Run a Physical Inventory Count in Sage X3
Sage X3 physical counts run through Stock > Counts: create a count session scoped to a site, category, or zone, generate the count sheet to freeze theoretical quantities, enter counted quantities, review the variance report, then validate to post stock and valuation adjustments. Blocking movements against the counted locations during the window keeps the variance meaningful.
How-toSage X3 Production Planning, Scheduling and Tracking
Sage X3 plans production from master data (items, BOMs, routings, work centers) through MRP or manual work orders, schedules operations against work center capacity, then records progress with production tracking. Setup quality in the BOM, routing and work center calendar decides whether the plan is believable.
Error fixDivision by 0 Error in Sage X3: Find the Cause and Fix It
A division by 0 error in Sage X3 means a calculation divided by a field that was zero or empty at runtime. Typical sources are a zero unit-of-measure coefficient, a zero quantity or base quantity on a BOM or routing, a zero price or rate, or custom 4GL or report code that never guards the denominator. Find the script and line from the error, then fix the data or guard the calculation.
How-toSage X3 Developer Studio: What It Does and How to Track Versions and Release Notes
Sage X3 Developer Studio is the development environment for building and changing X3 solution code and web pages, working with the Adonix 4GL scripts and the Syracuse web layer. To track versions, read the release notes and compatibility guides that Sage publishes for each version and patch rather than relying on remembered dates.
AI for ERPAI for accounts payable invoice matching in your ERP
On-prem AI reads vendor invoices, runs 3-way match against your ERP PO and receipt, and routes only real exceptions to your AP team. No invoice data leaves your network.
AI for ERPAI Agents for ERP, Running On-Prem
A practical guide to on-prem AI agents for ERP: what they can safely automate, where human approval belongs, and how to design the guardrails.
Stuck on Sage X3?
Talk to engineers who work inside Sage X3 every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Sage X3 Import Template WorksheetAn editable import tracker for Sage X3: which object, which import template, source file, records loaded, errors and owner, with error rates calculated.
- Sage X3 Database Tables ReferenceKey Sage X3 tables by module with what they store, typical key columns and naming conventions for SQL and reporting.
- Sage X3 Maintenance Checklist and ScheduleA tick-box routine maintenance plan for Sage X3: database, batch server, Syracuse, backups, patches, security and testing.
ERP fixes and how-tos
- Sage X3 AP automation: from invoice capture to postingHow to automate accounts payable in Sage X3: invoice capture, matching to receipts and orders, import and posting, approvals and what still needs a human.
- Sage X3 Production Planning, Scheduling and TrackingHow Sage X3 production planning works: master data, MRP, work orders, scheduling and shop floor tracking, and what to set up first. Practical overview.
- Sage X3 AI Integration On-Prem: A Private ArchitectureHow to add a private AI assistant to on-prem Sage X3: SQL read replica, Syracuse SData and web services, retrieval index, local GPU model and audit trail.
AI on your ERP
- AI for Sage X3, Grounded in Your Own Ledgers and Stock DataAdd AI to Sage X3 finance and stock data without exporting it to a public model. On-prem and private-cloud LLMs for Sage X3 in the UK and France.
- AI for Sage X3 Purchasing and Stock: Orders, Receipts and LotsAI for Sage X3 purchasing and stock: PO review, supplier delivery analysis, stock status and lot questions over X3 data using GraphQL, SOAP and private models.
Integrations
- How to add document OCR to Sage X3Capture supplier invoices, packing slips and certificates into Sage X3 with OCR, confidence thresholds, PO matching and human review. On-prem options covered.
- How to add an AI chatbot to Sage X3Add an AI chatbot to Sage X3 for staff, suppliers or customers: grounded in ERP data, respecting roles, with a fully on-prem option using open models.