• Just released: Sage X3 v12.0 1099 2022

    Just released: Sage X3 v12.0 1099 2022. We're thrilled to let you know that the Sage X3 v12.0 1099 for 2022 is now available to download from the Sage Knowledgebase. Head to Knowledgebase article Download Sage X3 Version 12.0 1099 2022 to download…
  • Function GESPAY Supplier cash payment Error: Open item being matched

    A/P-A/R accounting>Payments>Payment/Receipt(GESPAY)> SCAS Supplier Cash Payments> For Advance payment entry, every time a user tries to create the entry faces the following error. need urgent help. X3 Application error: Open item being matched.. …
  • Non-existent variable BOX

    I'm getting this error "Error 6: Non-existent variable BOX", but I can't access GSAISIE so I don't know what variable BOX does. Has anyone had this error and managed to solve it?
  • Invoice won't post and errors with "Unbalanced Distribution"

    Our Customer Service team started receiving this error when posting some invoices: "CI2200860 ZSIHI : Unbalanced Distribution 4 (ZSIHI Line 410)" and I'm not having any luck resolving it. I have run GTEST to check the posted amounts and they balance.…
  • Unbalanced Journal Legal Error - Unable to Post Invoice

    We are using X3 version 11. I have been invoicing and posting for the same customer without issue until today. Now I am unable to post any new invoices. Seems to be with just this customer though. Error message just says "Unbalanced Journal Legal Rollback…
  • Error in payment posting

    Hi all, When select the "Post" button on a payment, the following error appears: PAYMEP: Unauthorised function . This happens for a specific payment transaction and a user. Do you know what is causing this? Thank you.
  • Table: STOCK[STO] Key: #### No current records When deleting a Subcontract Order

    I am trying to delete a subcon record. I am getting the following error. Table: STOCK[STO] Key: #### No current records Nothing has been done against the subcon.
  • what does "Rollback following error in transaction" mean?

    My user noticed this message in the log after they ran automatic allocations. Unsure what the message means though.