Kumusoft Solutions
EFRIS API
EFRIS API
  1. ๐Ÿ“‹ Reference
  • ๐Ÿš€ Getting started
  • ๐Ÿ” Authentication
    • Getting started
    • Calling Kumusoft APIs
    • API Keys
    • Generate auth Token
      POST
  • ๐Ÿงพ Invoicing
    • How to generate a Fiscal invoice
    • Generate fiscal invoice
      POST
    • Preview fiscal invoice
      POST
    • Search invoices
      POST
    • Invoice detils
      GET
  • ๐Ÿ“ฆ Stock Management
    • All stock items
      GET
    • Search stock items
      POST
    • Reduce stock
      POST
    • Increase stock
      POST
    • Register stock item
      POST
  • ๐Ÿ“ƒ Credit Notes
    • Issue credit note
      POST
  • โš™๏ธ Masterdata
    • Registration details
      GET
    • Get Masterdata
      GET
  • ๐Ÿ“‹ Reference
    • Overview
    • Data Sources
    • Invoice Types
    • Tax Rules
    • Return Codes
      • Overview
      • General system return codes
      • Taxpayer return codes
      • Invoice return codes
      • Credit note return codes
      • Stock management return codes
      • Device return codes
      • Invoice industry codes
  1. ๐Ÿ“‹ Reference

Data Sources

Data Source identifies the channel through which a transaction is submitted to EFRIS.
The EFRIS platform supports multiple submission channels. However, integrations built using the Kumusoft EFRIS API should typically use 101 (System to System).

Data Source Codes#

CodeDescription
101System to System
102Web Portal
103Mobile Application
104Desktop Client
105Electronic Fiscal Device (EFD)
106POS System
107USSD
108AskURA

Recommended Value#

For all integrations using the Kumusoft EFRIS API, the recommended value is:
{
  "dataSource": "101"
}

101 - System to System#

Indicates that the transaction was submitted through a direct API integration.
Examples include:
ERP systems
Accounting software
Billing platforms
E-commerce systems
Custom applications
Middleware platforms
This is the value used by most Kumusoft EFRIS API integrations.

Other Data Sources#

The following values are defined by EFRIS and may appear in existing EFRIS documentation or legacy implementations:
CodeDescription
102Web Portal
103Mobile Application
104Desktop Client
105Electronic Fiscal Device (EFD)
106POS System
107USSD
108AskURA
Unless specifically instructed otherwise, developers integrating through the Kumusoft EFRIS API should continue to use 101 (System to System).

Related Documentation#

Invoicing
Credit Notes
Stock Management
Interface Codes
Best Practice: Use 101 for all new integrations unless your implementation requires a different EFRIS-defined channel.
Previous
Overview
Next
Invoice Types
Built with