GST Ledger Import

Imports ledger records from uploaded files and returns processed records, validation results and file-level errors where applicable.

API Details

Method: POST

Endpoint: /gst-recon/import

Base URL: https://uatapi.wowpe.in/api/api/api-module

Authentication

Header	Type	Description
X-Client-Id	String	Client ID provided by WowPe.
X-Client-Secret	String	Client secret provided by WowPe.

Request Parameters

Content-Type: multipart/form-data

Parameter	Type	Mandatory	Description
files	File	Yes	Ledger file(s) to import. Repeat this field for multiple files.

Supported Input Formats

The available ledger reader supports:

• CSV
• XLSX
• Flat JSON row arrays
• Flat XML rows

The reader uses the first worksheet for Excel files. Confirm deployed format support with the API owner before relying on it in production.

Expected Ledger Columns

Use the following canonical column names or confirm the correct source-column mapping with the API owner.

Column	Description
BeneficiaryName	Supplier or beneficiary name.
UniqueRefNo	Invoice or reference number.
TaxableValue	Taxable amount.
CGST	Central GST amount.
SGST	State GST amount.
IGST	Integrated GST amount.
GSTAmount	Total GST amount.
Gstin	GST identification number.
DocumentDate	Document date.
DocumentType	Document type.

BeneficiaryName and UniqueRefNo are required by the available reader.

Sample Request

Bash

curl --request POST 'https://uatapi.wowpe.in/api/api/api-module/gst-recon/import' \
  --header 'X-Client-Id: YOUR_CLIENT_ID' \
  --header 'X-Client-Secret: YOUR_CLIENT_SECRET' \
  --form '[email protected]'

Sample Response

JSON

{
  "reviewRequired": true,
  "files": [
    {
      "fileName": "ledger.csv",
      "success": true,
      "rows": [
        {
          "sourceFile": "ledger.csv",
          "line": 1,
          "beneficiaryName": "Example Supplier",
          "uniqueRefNo": "0007",
          "gstin": "27ABCDE1234F1Z5",
          "documentDate": "2026-04-01",
          "documentType": "Invoice",
          "taxableValue": 1000,
          "cgst": 90,
          "sgst": 90,
          "igst": 0,
          "gstAmount": 180,
          "reviewed": false
        }
      ]
    }
  ]
}

Note: Illustrative response based on the documented response structure. Actual fields may vary.

Response Parameters

Parameter	Type	Description
reviewRequired	Boolean	Indicates whether imported records require review.
files	Array	Contains file-processing results.
fileName	String	Name of the processed file.
success	Boolean	Indicates the observed processing result for the file.
rows	Array	Contains imported ledger records.
sourceFile	String	Source file name, where returned.
line	Number	Source row or line reference, where returned.
beneficiaryName	String	Supplier or beneficiary name.
uniqueRefNo	String	Invoice or reference number.
gstin	String	GST identification number.
documentDate	String	Document date.
documentType	String	Document type.
taxableValue	Number / Null	Taxable amount.
cgst	Number / Null	Central GST amount.
sgst	Number / Null	State GST amount.
igst	Number / Null	Integrated GST amount.
gstAmount	Number / Null	Reported or calculated GST amount.
reviewed	Boolean	Review status, where returned.

Error Handling

The earlier UAT tests included HTTP 422 Unprocessable Entity for input validation failures.

Common issues include:

• Missing required identity columns.
• Duplicate mapped column headers.
• Formula cells that have not been converted to reviewed values.
• Invalid numeric formats or unsupported amount precision.

Inspect the HTTP status and file-level success, errorCode and message fields where returned.

Important Notes

• Preserve invoice references and GSTIN values as text to avoid losing leading zeros.
• Keep blank amounts distinct from numeric zero.
• Do not assume that a successful file response means every row or worksheet was imported.
• The available reader's mapping options have not been confirmed as deployed API behaviour.
• Importing a ledger does not automatically make its data suitable for reconciliation if required tax components remain unknown.

What's Next

Review the imported rows, correct mapping errors and confirm that the ledger data is complete before submitting it to the reconciliation API.