The Customer & Supplier Portal is a separate, signed-in surface where each customer sees their own invoices and statement, and each supplier sees their own purchase orders and statement — read-only in this release. No shared logins, no finance-system access, no open URLs.
Customers call to ask whether an invoice arrived, whether a payment cleared, or what they still owe. Suppliers call the accounts payable desk to ask whether a bill was received and when it will be paid. Statements go out by email and go stale the moment a new invoice posts. None of this is dangerous work, but all of it consumes staff time that a self-service view could absorb — provided the two sides can never see each other's records, and provided giving that access doesn't mean handing out a login to the finance system itself.
Your team creates an explicit portal access record for a specific customer or a specific supplier — never a generic open link. Access is a business decision recorded against that one account, and it can be revoked the same way it was granted.
The customer or supplier signs in on a dedicated portal login, entirely separate from staff sign-in to the ERP application itself. They never touch the finance system's own screens, menus or data.
A customer's home page shows their own position, invoices and statement. A supplier's home page shows their own open purchase orders and their own statement of submitted bills and payment status — the exact question accounts payable fields most often.
The portal reads the same invoice, order and statement records the finance team works on directly, so there is no separate portal database to fall out of sync with what accounting actually posted.
Where a jurisdiction mandates e-invoicing, a cleared invoice shows the customer its clearance reference. Where a hosted pay link has been configured, a customer can settle an invoice from the link they were sent by e-mail or WhatsApp, without needing a portal account at all.
The portal is its own application with its own login screen, kept apart from the ERP application customers and suppliers must never enter. A customer or supplier signing in never sees a menu, a screen or a permission that belongs to your finance staff — only the small set of pages built specifically for them.
The moment a customer signs in they land on a home page summarising their own position with the business — outstanding balance and recent activity — rather than a blank dashboard or a menu they have to figure out on their own.
A customer can see every invoice raised against their account, current and historical, without a phone call to accounts. This is the single most common reason a customer contacts finance today, and it becomes a self-service lookup instead.
The customer's own account statement is available on demand instead of being emailed periodically and going stale the moment a new invoice or payment posts. The statement a customer sees is always the current one, not last month's snapshot.
The supplier side of the portal is new in Enfinity — the legacy product had no supplier-facing equivalent. A supplier signing in lands on their own home page summarising their standing with your business, the same idea as the customer home but built for the other side of the ledger.
A supplier sees the open purchase orders placed with them — what was ordered, in what quantity, and its current status — without emailing the buyer to ask. This is read-only visibility into orders your own procurement team raised; the supplier cannot create or amend an order from here.
A supplier sees their own submitted bills and payment status directly — exactly the question that otherwise lands on the accounts payable desk as a phone call or an email. The supplier reads their standing; they cannot post, dispute or amend a bill from the portal itself.
The supplier side of the portal is deliberately read-only in this release. A supplier cannot submit a bill, dispute a purchase order, or edit any record through the portal — they can only view what your team has already posted. We say this plainly rather than implying a submission workflow that does not yet exist.
Isolation between parties is the portal's central promise and its most heavily tested behaviour: one supplier can never see another supplier's orders or statement, and one customer never another customer's invoices. A record that doesn't belong to the signed-in party behaves as if it doesn't exist, rather than returning a permission error that confirms it does.
A customer can settle an invoice from a hosted pay link sent to them, without ever creating a portal account at all — useful for a one-off payer who will never need ongoing self-service. This is disabled by default until a signing key and base URL are configured, so it is never a live surface by accident.
Every portal sign-in and view falls under the same ERP audit trail as any other access to your data, so an access grant is not a blind spot — what a customer or supplier looked at is recorded the same way staff access is.
Portal pages carry the same bilingual fields and right-to-left rendering as the rest of Enfinity ERP, rather than a translated skin bolted onto an English-only surface. A customer or supplier reading Arabic sees names, labels and statements laid out correctly in Arabic, not a mirrored English layout with substituted text.
Where the jurisdiction mandates e-invoicing, a cleared invoice appears to the customer with its own clearance reference alongside it, so the customer's copy carries the same regulatory proof the business holds — not a plain PDF stripped of that detail.
A statement or invoice shows in the currency the document was actually raised in, not converted into a single reporting currency for display. A supplier billing in one currency and a customer invoiced in another each see their own figures the way they were recorded.
The tax detail a customer sees on a portal invoice — VAT breakdown and clearance reference where applicable — is live for Saudi Arabia, the UAE, Bahrain and Oman today. Kuwait and Qatar are ready to configure the moment either introduces VAT; Kuwait currently has no VAT to configure for.
| Small | Standard | Professional |
|---|---|---|
| Not included at Small — invoices and statements are shared by email or on request until self-service volume justifies a portal. | Included | Included |
CRM keeps its own customer and opportunity record for sales; the portal exposes only the finance-facing invoice and statement view of that same customer, so the two stay purposefully separate rather than merged into one screen.
A subscription customer billed through Enfinity Billing can be the same customer who signs in here for a statement, giving recurring-revenue customers one place to check both a subscription invoice and their broader account position.
The invoices and statement a customer sees in the portal are the same records the collections and credit-control team works from, so a self-service view and an internal ageing worklist never disagree about what a customer owes.
This is the one surface where someone outside your organisation signs in at all, so the platform's identity and MFA controls matter here more than almost anywhere else in Enfinity ERP — a customer or supplier account is provisioned and secured the same rigorous way a staff account is.
A customer or supplier's records are scoped to the legal entity they actually trade with, so a group with several companies never shows one company's invoices inside another's statement.
Statements and invoices in the portal render from the same document templates finance uses internally, so a customer's copy always matches the layout, branding and numbers the finance team itself would print.
There is no AI feature in the portal. Internal finance advisories — collection reminder drafts, ageing risk and collection prioritisation — are tools the finance team uses on its own screens; they never run inside the portal, and nothing generated by them is ever auto-sent to a customer or supplier.
No. The supplier side of the portal is read-only in this release: a supplier can view their open purchase orders and their statement of submitted bills and payment status, but cannot edit, dispute or submit anything through the portal itself. A supplier submitting documents through the portal is a natural future direction, not a shipped capability today.
Isolation between parties is the portal's primary guarantee and its most heavily tested behaviour. A supplier can never see another supplier's orders or statement, and a customer never another customer's invoices — a foreign record simply behaves as if it does not exist, rather than surfacing a permission error that would confirm it does.
Yes. The portal carries the same bilingual fields and right-to-left rendering as the rest of Enfinity ERP, so a customer or supplier reading Arabic sees names, statements and invoices laid out natively in Arabic rather than a mirrored translation of an English screen.
No. The portal is a responsive web surface that works on a phone browser, but there is no dedicated portal mobile application. Enfinity ERP's own mobile app is built for your staff, not for the customers and suppliers who sign into the portal.
There is no separate portal data store to configure — the portal reads the same invoice, order and statement records your finance team already works on. The setup work is granting an explicit access record per customer or supplier you want to give access to, not standing up a new system.
Saudi Arabia, the UAE, Bahrain and Oman are active today, so a customer in any of those jurisdictions sees the correct VAT breakdown and, where mandated, the clearance reference on a cleared invoice. Kuwait and Qatar are ready to configure once either introduces VAT.
There is nothing separate to publish. The portal reads the same invoice, order and statement records the finance team posts directly in the ERP application, so an invoice appears to the customer the moment it exists — not after a separate export or sync step. Delivery outside the portal, such as a WhatsApp notice when an invoice is issued, goes through the platform's own notification channels.
