Messages Journal Entries can show

This entry has already been posted.

This entry has already been reversed.

Line {line} carries both a debit and a credit. A line carries one or the other.

A posted entry cannot be changed. Reverse it and post a correction.

Add at least one line.

{code} is no longer in use and cannot be posted to.

Enter a date in the form YYYY-MM-DD.

Every line on one entry must be in {expected}. A line was found in {found}.

Line {line} carries a negative amount. To undo a posting, reverse it — never post a negative.

That entry does not exist.

This entry has not been posted.

A reversal cannot be reversed. Post a new entry instead.

An entry needs at least two lines — one debit and one credit.

This entry does not balance and was not saved. Debits {debit}, credits {credit} — a difference of {difference}.

That account does not exist.

Line {line} has no amount. Enter a debit or a credit.

This product does not recognise {source} as a journal source. An entry's source is what decides which lock date it answers to, so it cannot be guessed at.

An entry cannot be declared as {source}. Opening balances and the year-end close bypass every lock date, and they are posted by the routines that own them.

A city-ledger transfer moves a balance between the guest ledger and a company's account. Account {code} is neither, so this entry cannot be posted as one. The revenue was already recognised when the charge was posted to the folio.

The guest-ledger and city-ledger control accounts have not been set, so a transfer between them has nowhere to post. Set both in Accounting settings.

Point of Sale is not linked to the general ledger, so this session was not posted. Turn on the POS sales link in app links first.

A transfer to a company account is not a payment. Nothing was received, so it must not be posted to cash or a bank — post it as a city-ledger transfer.

The books are kept in {expected} and this charge is in {found}. A charge is posted in the currency it was converted to on the folio, never converted a second time here.

This charge states an amount in {currency} without saying how many decimal places it carries. An amount is minor units and a precision together.

{currency} is kept to {expected} decimal places in these books and this charge states {found}. Posting it would restate the amount, so it was refused.

This charge has no amount, so there is nothing to post.

A charge carries its amount as a positive figure and its class decides which way the balance moves. To undo a posting, reverse it — never post a negative.

This product does not recognise {class} as a folio transaction class, so it cannot know which side of the books the charge belongs on.

A transfer to the city ledger must name the company the balance is owed by.

There is no till session {session} to post.

There is no folio charge {document} to post.

Folio charge {document} was voided, so there is nothing to post. A void that already reached the ledger is corrected by reversing its entry, never by posting the charge again.

Hotel is not linked to the general ledger, so this charge was not posted. Turn on the hotel folios link in app links first.

Till session {session} is still open. A session is posted after it has been closed and its drawer counted.

Till session {session} was closed without a cash count, so there is no final figure to post.

Till session {session} carries no business date. A posting takes the trading day from the session and never from the clock.

Sale {sale} was charged to a room. That revenue reaches the ledger through the guest folio, so the till session must not post it a second time.

Till session {session} has {count} drawer movements with no account to post them to. Record them as expenses or receipts before posting the session.

The totals recorded on {document} do not add up: {figure} is out by {difference}.

Till session {session} recorded no sales, no refunds and no cash difference. There is nothing to post.

There is no payroll run {run} to post.

Payroll run {run} has not been marked as paid. A run reaches the books once, on the day it is paid.

Payroll run {run} does not agree with its own payslips ({field}), so it was not posted. The books never carry a payroll figure the payslips do not support.

Payroll run {run} was paid in {found} on {paidOn}, and these books are kept in {expected}. No {found} rate on file was known on that day, so the run was not posted. Add the rate in Company settings under Currencies, or post the run by hand at the rate your bank used.