Events

The package builds official Event XML for the event types currently supported by the domain layer:

Event ID

const eventId = efatura.buildEventId({
  issueDateTime: '2026-02-08T11:30:00',
});

The Event ID is a 24-character value containing country, repository code, issue date and time, and transmitter NIF.

You can pass repositoryCode and transmitterNif to override config values for a specific event.

FDC

const xml = efatura.buildEventXml({
  type: 'FDC',
  issueDateTime: '2026-02-08T11:30:00',
  issueReasonDescription: 'Documento emitido com dados incorretos.',
  iuds: [
    'CV3260208100200300001230100000000112345678909',
  ],
});

Rules:

• issueDateTime must be a valid ISO date-time.
• issueReasonDescription is required.
• iuds must contain at least one valid IUD.
• Range data is not accepted for FDC.

UDN

const xml = efatura.buildEventXml({
  type: 'UDN',
  issueDateTime: '2026-02-08T11:30:00',
  issueReasonDescription: 'Sequencia nao utilizada.',
  range: {
    year: '2026',
    ledCode: '123',
    serie: '123',
    documentTypeCode: 1,
    documentNumberStart: 10,
    documentNumberEnd: 12,
  },
});

Rules:

• issueDateTime must be a valid ISO date-time.
• issueReasonDescription is required.
• range is required.
• documentTypeCode must resolve to a supported document type.
• documentNumberStart and documentNumberEnd define the unused range.
• IUD lists are not accepted for UDN.

Options

const xml = efatura.buildEventXml(event, {
  id: eventId,
  emissionMode: 'Online',
});

Validation

const event = efatura.validateEvent(rawEvent);
const xml = efatura.buildEventXml(event);
const result = await efatura.validateEventXml(xml);

validateEvent() applies domain validation. validateEventXml() delegates to the configured XSD validator.

HTTP Adapter

await fetch('/efatura/event/xml', {
  method: 'POST',
  credentials: 'include',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({
    event,
    options: { emissionMode: 'Online' },
  }),
});

The response body is:

{
  "xml": "<Event>...</Event>"
}

Keep event creation on the server side when the event depends on fiscal-number recovery or cancellation approvals.