Alya Books

    ERP and systems

    Your ERP stays. Your processes stay. E-invoicing joins them.

    Receiving, checking, approval and reporting to the FTA run through Alya Books: via Peppol, connectors, the REST API and accounting exports. Your ERP stays the system of record.

    • No system switch
    • Ready to use immediately
    • No IT project required

    Connects to

    ERP, accounting, payments and your bank.

    • QuickBooks Online

      Accounting connector · OAuth; pull customers and invoices, push issued invoices

    • Xero

      Accounting connector · OAuth; pull contacts and invoices, push issued invoices

    • Odoo

      Accounting connector · JSON-RPC; partners and customer invoices both ways

    • Zoho Books

      Accounting connector · OAuth; invoices and contacts

    • Tally

      Import and export · XML vouchers in and out

    • Stripe

      Payments · Pay-by-link checkout and webhooks

    • Telr

      Payments · UAE gateway, hosted page

    • PayTabs

      Payments · GCC gateway, hosted page

    • Tap

      Payments · GCC gateway, hosted page

    • Lean Technologies

      Bank feeds · Open banking transactions

    • Tarabut

      Bank feeds · Open banking transactions

    • REST API

      Everything else · 153 operations, webhooks, MCP, CLI

    Status quo

    Every manually transferred invoice costs time and risks errors.

    Broken data handoffs, duplicate entry and missing status feedback tie up your team and jeopardise clean, auditable data in the ERP.

    Manual data entry

    Invoice data is checked several times, adjusted or transferred by hand between the accounting system and the ASP portal.

    Format conversions

    Accounting systems export CSV or PDF; the FTA wants PINT AE. Someone converts, and errors creep in.

    No status synchronisation

    Reported? Rejected? Paid? The answer lives in three systems and a spreadsheet.

    How it fits

    Alya Books connects invoicing with your existing systems.

    Invoices are received, validated and approved before they are handed over to the ERP in structured form; issued invoices flow back.

    1. 01

      Receipt

      All incoming invoices arrive in Alya Books first: Peppol, email, upload or API.
      • Peppol
      • Email
      • Upload
      • API
    2. 02

      Validation

      Every invoice is validated against PINT AE, including a validation report.
      • PINT AE
      • Report
    3. 03

      Review and approval

      Invoices are reviewed in a structured way and approved with a complete log.
      • Workflow
      • Log
    4. 04

      ERP handover

      Structured data goes to the ERP or to accounting: connector sync, REST API, webhook, CSV or Tally XML.
      • Connectors
      • API
      • Webhooks
      • Exports

    Result: Clean data in the ERP. No duplicate entry. Full traceability.

    How companies use Alya Books

    The ERP remains the system of record.

    Companies place Alya Books in front of and behind their ERP: incoming invoices are validated and handed over in structured form, outgoing data leaves the system in PINT AE and is reported, webhooks report status changes back. No system change, no data migration, no parallel operation.

    Compliance

    Compliance that takes care of itself.

    FTA reporting

    Through Taxilla, an accredited service provider; the timeline stays on the invoice.

    Data protection

    Encrypted in transit and at rest; a data processing agreement is part of the terms.

    Access and audit

    Roles, granular permissions and an audit log of every financial action.

    Your systems stay. The manual work goes.

    Connect Alya Books to your ERP, and your invoice data flows straight through.

    Free Starter plan · No card · Cancel any time