Skip to main content

​
Overview

A Mexican global invoice is a CFDI that groups eligible sales to the general public (público en general) over a reporting period. It is not a generic subscription invoice for named customers. Confirm the issuer and transaction qualify for the intended period using the SAT’s global-invoice filling guide. In gigstack you issue one by adding a global object to an income invoice (POST /v2/invoices/income, or a draft with POST /v2/invoices/draft). gigstack can also issue them automatically at the end of each month from your pending receipts; see End-of-Month Global Invoicing.

​
The global Object

The public schema checks the field types but does not establish that the combination is fiscally valid. Check the period, year, issuer regime, and issuance date together before stamping; provider validation can reject an inappropriate combination.

​
Periodicity Codes (c_Periodicidad)

months is a separate field: 01–12 name calendar months, and 13–18 name bimesters. For example, August monthly reporting uses periodicity: "04" and months: "08". Bimester reporting is not available to every issuer merely because 05 appears in the catalog; confirm the applicable regime and SAT rules first.

​
The Receiver

A global invoice is addressed to the general public. These are the SAT’s rules for the receiver of a global invoice: gigstack’s built-in general-public client uses PUBLICO EN GENERAL, XAXX010101000 and regime 616.

​
Example

The following is a request-body fragment showing the global period and recipient fields for August 2026. It is not a complete request: add the actual source-sale items, payment information, and other required fields from the income contract, or prepare a draft for review.
Replace ISSUER_POSTAL_CODE with the issuer’s actual fiscal issuance postal code. This fragment is schema-shaped documentation, not an end-to-end verified global invoice example. Do not aggregate arbitrary sales into one synthetic line or reuse a named-customer tutorial’s items without applying the global-invoice rules. Before issuance, reconcile the underlying receipts: exclude sales already individually invoiced or already included in another global. After issuance, save the UUID and inspect its receiver, period, included sales, taxes, and totals. If a customer later requests an individual invoice, follow the motive 04 cancellation and reissuance workflow.

​
Team Settings That Affect Global Invoices

  • settings.global_invoice_disabled — turns off the automatic end-of-month global invoice.
  • settings.periodicity — the team’s default periodicity (day, week, two_weeks, month, two_months).
Read the settings through Get team. Change them through Update team settings. The update body uses global_invoice_disabled and periodicity directly, without a settings wrapper. Team periodicity words such as month are different from global.periodicity SAT codes such as "04". A scheduling setting does not establish fiscal eligibility.