IntegrationsCredits and refunds

Setting up credits and refunds

Three tables decide what a credit on a folio can say and where a refund’s money comes from. Get the cash ones wrong and your till will not balance at the end of the shift.

Where to find it
IntegrationsCredits and Refunds
Permission needed
Credit types.
Last checked
August 16, 2026

Two different things happen on this screen and they are easy to confuse. A credit reduces what a guest owes: it is a line on a folio and no money moves. A refund gives money back that has already been taken, so money does move and it has to come from somewhere real. Credit types configure the first. Refund source types and refund accounts configure the second.

The Credits and Refunds screen: three stacked cards, Credit types listing five named credits with their defaults, Refund source types listing bank transfer, payment gateway, cash drawer, petty cash and cheque with a code and a cash flag each, and Refund source accounts listing six accounts with their source type, linked drawer and GL code.
Three tables that between them decide what a credit can say and where a refund's money comes from. Each card has its own Add button.
  1. Credit types: the labels a folio credit can carry.
  2. Refund source types: the kinds of place money can come back from.
  3. Refund source accounts: the actual accounts staff pick from.

Three tables, and how they fit together

The second and third tables are a pair, and the order matters. A refund source type is a category, such as bank transfer or cash drawer. A refund source account is a specific account inside that category, such as your operating account or the front desk till. Every account belongs to exactly one source type, so you cannot create an account until the type it belongs to exists.

Staff never choose a source type when they post a refund. They choose an account. The type is what decides how that account behaves.

Credit types

The Credit types table with columns for name, description, deduct by default, credit note, approval and status. Goodwill Credit, Service Recovery, Loyalty Reward and Voucher Issued are Active; Promotional Discount is greyed out and marked Inactive with an Activate link.
The labels a folio credit can carry, and the defaults each one applies. A retired type stays on the list, greyed, so old folios still read correctly.

Each row is a label that will appear on a folio, plus three defaults that get applied when somebody adds it. Everything except the name is a default rather than a rule, so the person posting the credit can still change it on the folio.

The Add credit type dialog with a Name field, a Description box and four checkboxes: deduct from reservation total by default, generate credit note document by default, require manager approval before posting, and Active.
Everything except the name is a default that gets applied when somebody adds this credit to a folio.
FieldWhat it changes
Name What appears on the folio line and in the credit picker. Guests see this on their invoice, so write it the way you would want it read back to you in a complaint.
Description Internal only. It shows in this table and nowhere a guest can see, so it is the place to say when the credit should be used.
Deduct from reservation total by default On, the credit comes off the balance immediately. Off, it is recorded against the folio without changing what is owed, which is what you want for a credit the guest spends on a future stay.
Generate credit note document by default On, posting the credit produces a credit note. Turn it off only where your accountant does not need paperwork for that kind of adjustment.
Require manager approval before posting On, a clerk can select the credit but cannot complete it alone. Use it on the types that cost real money, such as a comped night, and leave it off the small routine ones or you will train your managers to approve without reading.
Active Off removes it from the picker without deleting it. See below.

Refund source types

The Refund source types table with columns for name, code, description, cash, accounts and status. Bank transfer, payment gateway, cash drawer, petty cash and cheque each show a code in monospace, and cash drawer and petty cash are the two marked Yes under Cash.
The kinds of place money can come back from. The Cash column is the one that matters: those two need an open drawer session before a refund can be paid.

A source type answers one question: what kind of place does this money come out of. The Cash column is the one that changes what happens, because it is the difference between a refund that is a book entry and a refund where somebody opens a drawer and counts notes out of it.

The Add source type dialog with Name and Code fields, a hint under Code reading that four codes are reserved and change how a refund is paid, a Description box, and checkboxes for paying out physical cash and for Active.
The hint under Code is the important part. Four values are reserved and change behaviour rather than just labelling it.

The checkbox marked Pays out physical cash is what sets that column. Tick it and every account under this type will demand an open drawer before a refund can be completed.

The four reserved codes

Code is normally just an identifier you choose. Four values are not: they are reserved, and typing one of them changes how the product treats refunds from that type.

CodeWhat it makes the type do
bankRefunds are matched automatically against your bank feed, so they reconcile without anybody touching them.
payment_gatewayRefunds go back through the processor to the card the guest paid with, and are matched against the gateway's own settlement.
cash_drawerRefunds are recorded against an open drawer session and appear in that session's activity.
petty_cashThe same, for an outlet float rather than the main till.

The codes are written exactly as shown, in lower case with an underscore. A type whose code is anything else is an ordinary type: it will work, it will just be reconciled by hand.

Refund source accounts

The Refund source accounts table with columns for name, source type, linked drawer, GL code and status. Front Desk Cash Drawer and Night Audit Cash Drawer are linked to drawers of the same name, Marlowe Operating Account, Card Settlement and Pool Bar Float are Not linked, and Legacy Cheque Account is Inactive.
The individual accounts staff choose from. Only the cash ones point at a drawer; the rest show Not linked.

These are what staff actually choose from. Each one names a source type, an optional linked cash drawer and a GL account code.

FieldWhat it changes
Name What the person posting the refund sees. Name it after the thing, not the category: Pool Bar Float tells a clerk which one to pick, "Petty cash 2" does not.
Source type Which category this account belongs to, and therefore how it behaves. Changing it on an existing account changes the behaviour of every future refund from it.
Linked cash drawer Only appears when the source type pays out physical cash. It names which drawer the money leaves.
GL account code Where the refund posts in your chart of accounts. Several accounts can share one code, which is normal: three cash accounts all posting to your cash on hand account is correct.

Why a cash refund needs an open drawer

The Edit refund account dialog for Front Desk Cash Drawer, showing Source type set to Cash drawer, a Linked cash drawer field set to Front Desk with a hint that a cash refund from this account is recorded against the open session on that drawer, a GL account code of 1000 and an Active checkbox.
The Linked cash drawer field only appears once you choose a source type that pays out physical cash.

Linked cash drawer only appears once you have chosen a source type that pays out physical cash. An empty Add dialog will not show it, which is why the figure above is an existing account being edited.

A cash drawer holds a session: somebody opens it with a counted float, every payment and refund through it is recorded against that session, and at the end of the shift somebody counts it and the count is compared against what the session expected. A refund paid from a linked account is one of the movements in that arithmetic.

Which is why a cash refund cannot be posted with no session open. There would be nothing to record it against and the next person to count that drawer would find money missing with no explanation. If your staff report that they cannot complete a cash refund, the drawer is closed; that is the first thing to check, before anything on this screen.

Retiring something you no longer use

Nothing on this screen deletes. Deactivate greys the row and takes it out of the pickers, and Activate puts it back. That is deliberate: a folio from last year that carries a credit type you have stopped using still has to render correctly, and deleting the type would leave a line with no label on a document you may have to produce.

One consequence worth knowing. The account picker on the drawer form lists active accounts only, so deactivating an account that a drawer points at leaves that drawer pointing at something nobody can select. Deactivate the account first, then repoint the drawer, rather than the other way round.

Who can change this

Two separate permissions cover this screen, and neither is granted to front desk staff by default:

PermissionWhat it allows
Credit types. Opening this screen, and adding or editing a credit type.
Refund source types and refund accounts. Adding or editing a source type or an account.

A clerk who could add a credit type could invent a reason to take money off a bill, and a clerk who could edit a refund account could point a refund at a different pot. Both are held back on purpose. A user without either sees a page telling them which permission they are missing and to ask an administrator for it under Users, User Roles.

Once this is set up, the screens that use it are posting charges, payments and refunds, where a credit or a refund is actually put on a folio, and the transaction report in finance reports, which is where you check that a day's cash refunds and takings agree with what the drawer counted.

Common questions

  • What is the difference between a credit and a refund?

    A credit reduces what the guest owes and no money moves. A refund returns money that has already been taken, so it has to come out of a real account. Credit types configure the first; refund source types and accounts configure the second.

  • Why can my staff not complete a cash refund?

    Almost always because the drawer has no open session. A refund from an account whose source type pays out physical cash is recorded against the open session on the linked drawer, and there is nothing to record it against when the drawer is closed. Open the session and try again.

  • Can I delete a credit type we no longer use?

    No, and you should not want to. Deactivate it instead. It disappears from the pickers and stays available to old folios, which still have to render the label they were posted with.

  • Why do several refund accounts have the same GL code?

    Because they post to the same place in your chart of accounts. Three cash accounts all posting to cash on hand is correct and normal. The GL code says where the money lands in the books; the account name says where it physically came from.

  • Do I have to use the reserved codes?

    Only if you want the behaviour attached to them. A source type with any other code works fine, it just will not be matched automatically against a bank feed or a gateway settlement, and it will not require an open drawer. That means somebody reconciles it by hand.

Was this article helpful?

Related articles

Still stuck?

Support answers from inside the app as well, so if you are already signed in you will get a faster reply there. Otherwise send us the property name and what you were trying to do.