Fac-360
Companies

Open a period, which sends nothing to SUNAT

ADMIN and above. Opening a period is a row in our ledger saying somebody intends to work on this month; nothing leaves for SUNAT and nothing is committed. A company still issuing in BETA is refused by the database, by the trigger migration 000080 installs, and this route only translates that refusal. Keeping the check in the database means the second entry point cannot forget it.

POST
/console/v1/companies/{companyId}/sire/periods/{book}/{period}

ADMIN and above. Opening a period is a row in our ledger saying somebody intends to work on this month; nothing leaves for SUNAT and nothing is committed.

A company still issuing in BETA is refused by the database, by the trigger migration 000080 installs, and this route only translates that refusal. Keeping the check in the database means the second entry point cannot forget it.

Authorization

consoleSession
__Host-apf_console<token>

Set by POST /console/v1/sessions. HttpOnly, Secure, SameSite=Strict, Path=/, __Host- prefixed. It is never readable by JavaScript and there is no header alternative: accepting both carriers would let an attacker choose the weaker one.

In: cookie

Path Parameters

companyId*string
Formatuuid
book*string

Value in

  • "rvie"
  • "rce"
period*string
Match^[0-9]{4}(0[1-9]|1[0-2])$

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/console/v1/companies/497f6eca-6276-4993-bfeb-53cbbbba6f08/sire/periods/rvie/string" \  -H "Authorization: Bearer apf_v2_tu_credencial"
{  "schemaVersion": "console.1",  "requestId": "d385ab22-0f51-4b97-9ecd-b8ff3fd4fcb6",  "book": "rvie",  "period": "string",  "status": "string",  "ticket": "string",  "sunat": {    "code": "string",    "message": "string"  },  "updatedAt": "2019-08-24T14:15:22Z"}

The SIRE periods this company has opened, newest first GET GET

ADMIN and above, which is the same floor migration 000081 gave sire:read and sire:manage, so a person role and a credential scope cannot disagree about who may close a tax period. It runs on DB_RUNTIME and not on the console connection, for the reason every company-scoped console route does: apifact_console holds SELECT on exactly two tables and cannot read sire.*, while auth.bind_console_company can prove which company this session is entitled to. The book is named rvie or rce and never the SUNAT codes 140000 and 080000. That translation lives in one module, which is where nobody gets it wrong.

Download what SUNAT proposes, and stop POST POST

ADMIN and above. This LOOKS: it asks SUNAT for the proposal and does not accept it. It is a separate route from generation, and not the same route with a flag, for the reason the machine surface gives at length: the difference between looking and committing cannot live in a JSON field, because the day somebody leaves that field set a period is closed and there is no inverse operation. Answers 202 and hands the period to the durable cycle; poll the period listing for the outcome. A period fenced as AMBIGUOUS is refused with 409 and never retried automatically.