Business apps
A booking, sales or operations app pushes invoices, payments and expenses into Faas as proper entries.
Bank, LHDN MyInvois, payments and your business apps can all feed Faas. Every push carries an ID, so connecting twice never records twice.
Connect from Settings, under Integrations.

Your bank already knows your transactions. Your booking or sales system already knows your invoices. Faas connects to them, takes what they know and keeps it tidy, so the books fill themselves in.
In Settings, under Integrations, pick what you want to connect.
Sign in with your bank, your MyInvois details or your gateway. Faas stores the connection for you.
Bank lines, payments and invoices from your apps arrive in Faas, mapped to the right accounts using posting rules.
Easy Mode shows what needs a Yes or No. The rest is already done.
Faas is a standalone accounting app that connects to the tools around it. It is not tied to any single source app.
Transactions arrive without uploading a statement. Faas matches them to invoices and bills, and only asks about the unclear ones.
See bank reconciliationSubmit e-Invoices straight from Faas and keep the status on each invoice.
See e-InvoicePowers the pay link, so customers can pay by FPX, card or e-wallet, and the invoice updates itself.
See the pay linkA booking, sales or operations app pushes invoices, payments and expenses into Faas as proper entries.
Build your own connection. Create and read records through an open, documented API.
Faas tells your own system when something happens, such as an invoice being paid.
If your team has a developer, the REST API lets you create invoices, payments and expenses from your own system. Webhooks tell your system when something changes in Faas. Each record you push carries a source id and an idempotency key.
{
"source_id": "BK-20931",
"idempotency_key": "bk-20931-v1",
"customer": "Aisyah Trading",
"lines": [{ "item": "Website design", "amount": 2000.00 }]
}Every push from an app carries two labels. The source id says where the record came from, such as booking BK-20931. The idempotency key says which attempt this is. If the same key arrives again, perhaps because a network drop made your app retry, Faas recognises it and does not post it again.

Six words developers use, translated.
A way for one program to talk to another.
A message Faas sends when something happens.
The ID of the record in the app it came from.
A unique label for one attempt.
A rule that decides which accounts an imported document uses.
Transactions sent directly from your bank.
See what it feels like when the books look after themselves.