We’ve got answers to all your doubts around e-invoicing in Malaysia
Our FAQ section is designed to quickly guide you through common queries about our services, features, and processes. Whether you’re looking for detailed information or just a quick clarification, you’ll find everything you need here.
Questions for Evaluating E-Invoicing Software
Is the e-invoicing software compliant with LHDN’s current and upcoming requirements?
The Anusaar platform is fully compliant with current and upcoming LHDN (IRBM) e-invoicing requirements, aligned with guidelines up to Version 4.3 (March 2025).
Does it support real-time submission and validation of invoices with LHDN?
Real-time validation and submission are enabled via RESTful APIs integrated with the MyInvois Portal.
Can the system generate invoices in the required XML or JSON format for Peppol?
Yes, structured XML/UBL format compliant with Peppol e-Invoicing standards is supported.
Does it integrate seamlessly with existing accounting software (e.g., UBS, Autocount, QuickBooks)?
"There are various approaches for integrating with ERP modules, namely API, database, and SFTP integration. The choice of integration method depends on the specific ERP system and its version. For ERPs such as AutoCount, UBS, and QuickBooks, any of the above-mentioned integration methods may be applicable, depending on suitability. Additionally, custom connectors are available for certain systems to support more specific integration needs."
Is there an audit trail or version history for all invoice submissions and changes?
Whether the data is pushed from the ERP to the Anusaar portal or ingested via Excel upload, a history of all ingested data will be captured.
How does the software handle rejected invoices or errors flagged by LHDN?
Errors and rejection responses are captured with full error codes and detailed logs; resubmission is managed via correction workflows.
Are there features for bulk invoice uploads and automation?
Yes, batch uploads via CSV/Excel and bulk API submission with automated validation are supported.
What kind of data encryption and security measures are in place?
Encryption of data in transit (TLS 1.2+) and at rest (AES-256). Hosting infrastructure is ISO 27001 & ISO 9001 certified, located in Malaysia Amazon Web Service cloud.
Is the software cloud-based or on-premise? What are the pros and cons?
The solution is primarily cloud-based, hosted on Malaysia Cloud. However, on-premise deployment is possible through a custom project. The cloud option offers advantages in scalability, compliance, and continuous updates with the latest features and requirements. While the on-premise solution can also be updated, it requires individual attention and prior approval from the client.
What is the cost structure—subscription, one-time fee, or per-invoice charge?
Pricing is typically subscription-based, volume pricing available; quotations tailored per client scope.
Questions About Migration to Accounting Software
Can the e-invoicing software export data in formats compatible with accounting system (CSV, Excel, API)?
Export functionality via CSV, Excel, and APIs is fully supported.
Is there a built-in migration or sync tool between e-invoicing and accounting software?
Middleware/API-based near real-time sync tools available for major ERP/accounting systems. The transmission of data from accounting sytem to middleware solution is performed via patch (API integration) which supports in data sync on real time basis.
What historical data (past invoices, customer/vendor details) can be migrated automatically?
The portal supports to capture customer / vendor master data. For the legacy transactions, it requires addiotional mapping.
Are there risks of data duplication or loss during migration?
Risks minimized through pre-validation, reconciliation reports, and staging before production deployment.
How long does the migration process usually take?
Standard migration timeline is 6–8 weeks including development, UAT, and production deployment.
Is there a rollback or backup plan if migration fails or causes errors?
Backup snapshots are taken prior to cutover, with rollback plans in place for data restoration.
What technical support or onboarding assistance is available during migration?
Full support including onboarding, technical training, UAT assistance, and post-go-live monitoring is provided.
Will existing accounting entries automatically reconcile with e-invoice submissions?
API-based synchronization can be configured to map invoice records with accounting entries. Additionally, a value-added reconciliation feature is available, enabling comparison between sales data and the data submitted to the government portal for validation. Any discrepancies identified will be highlighted, allowing users to take immediate corrective action and mitigate the risk of future notices and audits by government authorities.
Are there user access controls during and after migration?
Yes, robust role-based access control (RBAC) model is available for administration and operations users.
Does the vendor offer training or user guides for post-migration use?
User training, onboarding manuals, and guided sessions are standard parts of the deployment package.
Questions on Self-Billed Invoices with New E-Invoicing Software
Does the software support the creation of self-billed invoices according to LHDN guidelines?
Full support for self-billed invoice creation and validation under LHDN requirements is available.
Is there an option to select “Self-Billed Invoice” as a specific invoice type?
Self-billed invoice type selection is configurable at invoice generation level. It is also tagged in the portal and can also be filtered under AP module.
Can I pre-set suppliers as self-billing partners for recurring transactions?
Yes, suppliers can be flagged within the master setup for recurring self-billing.
Does the software automatically populate mandatory fields required for self-billed invoices under the Peppol format?
Mandatory fields validation is enforced during creation as per Peppol UBL standards.
How does the software ensure the invoice is clearly marked and submitted as a self-billed invoice to LHDN?
Self-billing classification fields are auto-tagged during submission payload generation.
Can the system handle multiple types of self-billing transactions (e.g., commission, agriculture, services)?
Yes, flexible configuration allows multiple transaction types to be managed under self-billing.
Will the software validate and submit the self-billed invoice directly to LHDN’s MyInvois portal?
Direct API integration with MyInvois portal for self-billed invoice submission is supported.
How does the system manage LHDN rejections or validation errors specific to self-billed invoices?
Error handling framework captures specific error messages and routes transactions for correction/resubmission.
Does the system automatically post the self-billed invoice into the Accounts Payable module?
Posting to Accounts Payable is supported via API/middleware integrations depending on ERP capabilities.
Can it sync with supplier ledgers for payment tracking and reconciliation?
Supplier ledger synchronization available via ERP/API mappings.
How does the software differentiate between regular purchases and self-billed invoices in reporting?
Reporting tags differentiate self-billed vs standard invoices for compliance and internal audit.
Is there a built-in workflow to store or share validated self-billed invoices with the respective suppliers?
Secure archival and workflow-based sharing (email/URL) are available for validated documents.
Does the software provide an audit trail for self-billed invoice creation and submission?
Basic logging available; enhanced detailed audit trails customizable if required.
Are there separate reports for self-billed vs regular invoices for compliance and internal review?
Separate reporting views for self-billed vs regular invoices are configurable.
Can the system generate a list of all suppliers under self-billing agreements?
Supplier master data can be queried and exported to list all flagged self-billing suppliers.