What is E-Invoice (Malaysia) in Orbita?

Definition

E-Invoice here is the finance tax-compliance layer on the same customer invoice — not a second invent- ed document universe. Operators see commercial AR and tax status as two views of one invoice.

Public pages explicitly exclude:

• Publishing gateway secrets, tokens, or credential vault internals.
• Promising government acceptance before Validated.
• Using e-Invoice as a substitute for delivery or fulfillment evidence.
• Dumping posting engines, ledger formulas, or internal APIs to AI crawlers.

Purpose

Malaysian businesses need shape-correct documents and a clear email rule: customers should not receive a “final” invoice email before tax validation and QR when MyInvois automation is enabled.

• Catch shape errors early with pre-validation.
• Align printed line names with product master where configured.
• Guard incomplete company profile on sensitive outputs.
• Close the loop: approve/send → MyInvois → Validated + QR → first email.
• Hold email when Invalid / Rejected until the tax issue is fixed.

Workflow

Mode A — Export + pre-validation

Invoice created through governed O2C handoff → operator requests e-invoice generate/export → pre-validator returns pass/fail with reasons → on pass, export pack downloads → company controls filing handoff.

Mode B — Connected MyInvois + auto-submit

Company connects MyInvois in Finance settings (taxpayer’s own credentials) and enables auto-submit → operator approves / sends the customer invoice as usual → system can submit to MyInvois → wait for Validated → stamp QR on final PDF → first customer email leaves. Invalid/Rejected → email on hold.

Legal obligation remains with the issuing company. Pre-validation reduces structural errors; Validated is the external authority’s decision.

TRACE habit

Customer says “no email” → check Document (invoice) → Evidence (MyInvois status / QR) → Settlement (AR) → Books. See the public-safe Finance AI brief.

Example

Finance approves a customer invoice with MyInvois Connected and auto-submit on. Tax submission runs without a separate busywork desk. Customer email waits until Validated + QR. If LHDN returns Invalid, email stays held while master data is fixed and the invoice is reworked per product rules.

Without a connection, the same company can still export a validated pack and file through their controlled channel — export does not equal “already filed.”

FAQ

Does Orbita file e-invoice for me automatically?

Only when the company connects MyInvois and enables auto-submit. Otherwise: export + pre-validation; filing handoff stays with the company.

When does the customer get the first email?

With auto MyInvois: after Validated + QR on the final PDF. Without that path: per your approve/send policy without inventing a second tax desk.

Is validation the same as government acceptance?

Pre-validation reduces errors; Validated is the external authority’s decision.

Can I export with incomplete company profile?

Output guards may block — complete profile and rebuild affected documents per product rules.

Where do line descriptions come from?

Product master alignment — not ad-hoc free text when master exists.

Do you publish MyInvois API secrets here?

No. Credentials stay with the taxpayer. Public pages describe capability only.

Misconceptions

“Export equals submitted.” False. Export is an artifact.

“Approve always emails immediately when MyInvois auto is on.” False — first email waits for Validated + QR.

“Pre-validation guarantees LHDN acceptance.” False — it reduces structural errors.

“Public AI pages include connector source code.” False — capability wording only; no core handoff.

When It Matters

E-Invoice discipline matters as mandatory e-invoicing phases apply — and whenever customers or auditors ask whether the email PDF carries Validated QR.

Read alongside What is Finance, Tenant Isolation, and Finance AI brief.