Settings you'll actually touch

You’ll need: Taxes, Currencies, Languages, API keys — if you cannot see these, the module may be switched off for your business or outside your permissions. An administrator can change either.

The settings area is large and most of it is not your problem. This lesson covers the handful you will meet, and — just as usefully — which ones to leave alone.

Ones you will meet

Taxes. The tax rates your business applies. They are referenced by documents rather than typed into them, so a rate you edit changes what future documents calculate. Never edit a rate to fix one invoice: add the correct rate and use it, or the change quietly reaches everything else that references it.

Currencies. Which currencies your business trades in. Every amount belongs to one, so this list has to be right before people start entering money.

Languages. Which languages you publish in. Turning one on means translatable fields expect a value for it, so switch on the ones you genuinely serve and no more.

Business locations. Covered in its own lesson, and the one worth the most care.

API keys. Credentials that let other software read and write your data. Treat one like a password: it carries real permissions, so it is issued deliberately and revoked when no longer needed.

The pattern behind all of them

Settings are referenced, not copied. A tax rate, a currency, a location — documents point at them rather than taking a snapshot. That is why changing one is never a local edit, and why the safe move is nearly always to add a new entry and leave the old one alone.

   invoice ----points at----> tax rate 19.25%
   invoice ----points at----> tax rate 19.25%
   invoice ----points at----> tax rate 19.25%
                                    ^
                     edit this and you have edited
                     what all three of them mean

Ones to leave alone

A few settings look administrative and are anything but, because their consequences do not appear on the screen where you changed them.

Payment gateway accounts decide where customer money actually lands. SMS endpoints decide what leaves your business in your name. API keys hand another piece of software the rights of a member of staff. PDF templates and website templates change every future document and every public page at once.

None of these are dangerous to read, and it is worth knowing they exist. But a mistake in any of them surfaces later and somewhere else — in a payment, in a message a customer receives, in next month’s invoices — which is exactly what makes them hard to trace back. Leave them to whoever owns them, and ask rather than experiment.

You have finished

That is the whole of FeePrime Essentials. You now know the shape of the system — business, module, record — and the ideas that repeat everywhere in it: that every change is recorded and may need approving, that nothing is deleted, that history is always answerable, and that stock, cash and permissions all attach to something specific rather than floating in the business at large.

Everything else is one module’s particular fields. Take the course for the part of the business you work in, and keep staging.feeprime.com open while you learn it.