Acugnito
Try Live DemoRequest a Demo
Acugnito
Try Live DemoRequest a Demo
Product · How it works

See what happens inside, step by step.

Five short chapters on what Acugnito actually does when you buy, sell, get paid, set prices and serve customers — drawn from the system’s own rules.

Try Live Demoadmin/admin
01Two flows, one ledger

Buying and selling take different routes. They arrive at the same place.

Follow a purchase and a sale station by station. Every step that posts drops into the same chart of accounts, the same dimension rules, the same ledger.

The shared foundationOne chart of accounts · one set of dimension rules
Dimension resolution
General ledger0
Procure-to-Pay
Order-to-Cash
Procure-to-Pay · 01Vendor record

Vendor setup

Vendor record, payment terms, default financial dimensions.

Why it mattersEvery field on a purchase invoice can inherit from here — dimensions, currency, cash discount code.

Order-to-Cash · 01Customer record

Customer setup

Customer record, credit terms, default financial dimensions.

Why it mattersCredit-limit checks and default dimensions both key off this one record for every order that follows.

  1. Procure-to-Pay
  2. 01

    Vendor setup

    Vendor record, payment terms, default financial dimensions.

  3. 02

    Procurement

    A purchase order for an item, quantity, and location.

  4. 03

    Vendor invoice

    Matched against the PO and receipt — plus any freight or handling charges.

  5. 04

    Accounts Payable

    Dimensions resolve, the invoice posts to the ledger.

    Posts to the ledger
  6. 05

    Payment

    Scheduled and settled — cash discount applied if still earned.

    Posts to the ledger
  1. Order-to-Cash
  2. 01

    Customer setup

    Customer record, credit terms, default financial dimensions.

  3. 02

    Sales order

    Item, quantity, and location — with live inventory reserved.

  4. 03

    Sales invoice

    Posts the receivable — and the item's inventory and cost-of-goods-sold in the same step.

  5. 04

    Accounts Receivable

    Dimensions resolve, the invoice posts to the ledger.

    Posts to the ledger
  6. 05

    Collection

    Payment received — aging and cash discount tracked automatically.

    Posts to the ledger
General ledgerOne chart of accounts · one set of dimension rules
02The shared foundation

Every document goes through the same posting engine.

Pick a document and watch it post. Each line finds its account through the same rules, picks up the same dimensions, and lands in a voucher that must balance.

Document
Sales invoice
SINV-000184
Northwind Traders
Item
HF-200 × 400
Net amount
10,000.00
Sales tax 5%
500.00
Total
10,500.00
Financial dimensions
CostCenterCC_100RegionGCC_UAE

No dimensions set on the invoice — the customer’s default set is inherited

Resolver1/5
  1. Posting typeCustomer balance
  2. RuleCustomer posting profileTableGroupEXTAll
  3. Main account1200Accounts receivable
  4. DimensionsCostCenterCC_100RegionGCC_UAE
  5. Ledger account
Voucher
VCH-004218Sales invoice · SINV-000184
Ledger accountDebitCredit
Total0.000.00

A voucher cannot post until it balances

One posting raises the receivable, the tax, and the stock movement together — they cannot drift apart.

Sales invoices, purchase invoices, free-text invoices and payment journals all resolve through this one engine — one chart of accounts, one set of dimension rules.

03Getting paid

When, how and in how many parts — the system does the arithmetic.

Three instruments from the payments desk. Move them and watch the rules respond exactly as they do in the product.

A

The cash-discount window

Code 1%7: pay within 7 days of the invoice date and 1% comes off. Drag the payment date.

Discount windowStandard termsOverdue
Invoice dateMar 1Cash discount dateMar 8Due dateMar 31
Discount earned
Invoice
8,255.63
Discount base (incl. tax)
8,255.63
Cash discount
− 82.56
Customer pays
8,173.07

Settling posts two extra lines — Cash Discount Taken and Cash Discount Offset — and the invoice still closes in full.

Accounts receivable › Payments › Cash discounts
B

One invoice, paid in parts

A 12,000.00 USD invoice under three payment schedules.

5,000.0041.7%Mar 31
5,000.0041.7%Apr 30
2,000.0016.7%May 31
Allocation
Fixed
Amount
5,000.00
Payment per
Month

Equal fixed installments; whatever is left over becomes the final payment. Schedules are currency-specific, and optional minimum and maximum amounts are checked when the invoice posts.

Accounts receivable › Payments › Payment schedule
C

Fees that find the payment

A 2,000.00 payment. Every fee rule that matches fires — they stack, not compete.

  • CARD_FEECard · Any currency · 2.5%—
  • WIRE_FEEWire · Any currency · 15.0015.00
  • FX_FEEAny method · EUR · 1%20.00
Fees expensed to the ledger
35.00
Reaches the bank
1,965.00
Invoice settles for
2,000.00
Accounts receivable › Payments setup › Payment fee
04Pricing

One item, many prices — the most specific rule wins.

Trade agreements price by customer, group, quantity break and date. Change the sale and watch the engine choose.

HF-200 · Hydraulic filterItem group FILTERS · Standard price 12.00
Customer
Quantity 120

Ranges are half-open: From is inclusive, To is exclusive — so 100 belongs to [100, ∞), not [10, 100).

Order date
QuoteNorthwind Traders · HF-200 × 120
Price · R39.40
R5 · Discount % 1 · −3%9.12
R5 · Discount % 2 · −2%8.94
R4 · Discount % 1 · −5%8.49
Net unit price8.49
Line amount120 × 8.49 = 1,018.80
Posted trade agreementsTable beats Group beats All — on the customer and on the item.
  1. R1
    Price11.20
    All customersGroup: FILTERSQty [1, ∞)Until Jul 1, 2026
    Expired
  2. R2
    Price10.50
    Group: WHOLESALETable: HF-200Qty [10, 100)
    Quantity outside the range
  3. R3
    Price9.40
    Table: Northwind TradersTable: HF-200Qty [100, ∞)
    Wins — most specific
  4. R4
    Line discount5%
    All customersAll itemsQty [50, ∞)Find next
    Applies
  5. R5
    Line discount3% + 2%
    Group: WHOLESALETable: HF-200Qty [1, ∞)Find next
    Applies

Rules are published by posting a Trade agreement journal. Validation rejects duplicates and overlapping ranges, so the engine is never left guessing.

Accounts receivable › Price and discount › Trade agreement journals
Meanwhile — not part of either flow above

Customer service runs on its own clock.

Tickets never touch the ledger. They move through the statuses your team defines, against the response time their priority promises. Three real outcomes of the same workflow:

TICKET-000241MaintenanceHigh—

Monthly oil change and inspection

Created automatically from the “oil-change-monthly” template, on a rental agreement’s monthly schedule

Customer
Harbour Plant Hire
Assigned to
Unassigned
Created by
System
Status routePunched only where it stops
  1. NewInitial
  2. AssignedAuto on assign
  3. In progress 
  4. On hold 
  5. ResolvedStamps time
  6. CancelledNeeds reason
Status historyLive feed
  1. Waiting for the first status…
  • 01

    Opens itself

    Every new ticket lands in your Initial status and draws its number from the sequence you choose.

  • 02

    Moves on assignment

    Assign an agent and the ticket steps into your Assigned status — and the agent is notified in real time.

  • 03

    Keeps its own clock

    Each priority carries a response-time target. The status that stamps “resolved at” decides whether the SLA was met.

  • 04

    Asks why, and remembers

    Statuses such as Cancelled demand a reason. Every change — who, when, from what — is kept in Status history.

Ready to see it in action?

Explore the live demo yourself, or request a personalised walkthrough with our team.

Username: admin·Password: admin