Setting up payment methods accepted on site
How to enable and configure the site’s payment methods so daily closures match the actual takings.
Payment methods configured in Klyra must exactly reflect what is actually accepted at the till, otherwise the daily closure and POS reconciliation become inaccurate. Configuration is done per site and should be updated whenever a payment provider changes.
Methods available by default
Klyra ships with the most common restaurant methods, such as cash and cards, ready to use. Each site can enable or disable methods based on what it actually accepts at the counter.
Adding specific methods
Beyond the standard methods, you can add meal vouchers or other local payment instruments, giving each one a recognisable name that will show up in the cash closure and in reports.
- Cash and cards configured by default
- Meal vouchers can be added per site
- Custom name for each method
- Unused methods can be disabled
Consistency across sites
If several sites share the same payment provider, keeping the same method names across sites makes it easier to read consolidated reports at organisation level.
Effect on POS reconciliation
The methods configured here are the ones shown in the cash closure and compared with the amount imported from the POS: a missing or duplicated method is one of the most common causes of reconciliation discrepancies.
Cosa trovi in questa guida
- payment methods
- site configuration
- cash and cards
- meal vouchers
- payment fees
- consistency with the till
Passaggi
- Open Finance and select "Payment methods".
- Choose the site to configure.
- Enable the standard methods actually accepted.
- Add any specific methods such as meal vouchers.
- Give each method a clear name.
- Disable methods no longer in use.
- Check that methods match what is configured on the POS.
Problemi frequenti
- A method used at the till does not appear in the closure → method not enabled for that site → enable it in the payment methods configuration.
- POS reconciliation always flags the same amount → method name differs between POS and closure → align method names between the two systems.
- Too many methods disabled by mistake leave the closure incomplete → disabling done without checking actual till usage → re-enable the method and check history before disabling it again.
- Sites show different names for the same method in consolidated reports → configuration done per site without coordination → standardise names at organisation level.
Domande frequenti
Are payment methods the same across all sites?
No, each site configures its own methods, but using consistent names is recommended for consolidated reports.
Can I disable a method without losing history?
Yes, disabling prevents new use but does not delete past closures that already include it.
Do I need one method per card provider?
Usually a generic "cards" method is enough, unless you want to separate data by provider.
What happens if I add a method after months of activity?
The new method is available immediately for new closures, without affecting ones already recorded.
Guide collegate
Questa guida ti è stata utile?
Hai ancora bisogno di aiuto?
Descrivi il problema: alleghiamo in automatico pagina, sede, organizzazione e ruolo.
Contatta l’assistenza