Skip to main content

MGCLatticeGeneralLedgerJournalService.reverseJournal

Reverses a posted ledger journal - every voucher, or the one Voucher names - the way the posted journal's Reverse does: each voucher is reversed by the standard engine the transaction reversal providers choose for it (general ledger only: TransactionReversal_Ledger; a customer or vendor transaction: TransactionReversal_Cust / TransactionReversal_Vend; a customer payment posted to a bank account: BankPaymCancel). Every voucher is reversed in one transaction, so either all are reversed or, when one fails, none is.

  • HTTP method: POST
  • Route: /api/services/MGCLatticeGeneralLedgerServiceGroup/MGCLatticeGeneralLedgerJournalService/reverseJournal
  • Service class: MGCLatticeGeneralLedgerJournalService

Parameters​

NameTypeOptionalDescription
_requestMGCLatticeJournalReversalRequestContractNoThe request containing JournalNum (or JournalNumExternalKey, or a Voucher of the journal), the optional Voucher, ReversalDate, ReasonCode and ReasonComment, and the standard header fields.

Returns​

MGCLatticeOrderOperationResponseContract

An MGCLatticeOrderOperationResponseContract: DocumentId is the reversed journal, PostedDocumentId the reversal voucher of its first voucher, and the message lists every reversal voucher.

Security​

  • Requires privilege MGCLatticeGeneralLedgerJournalReverseMaintain