My Oracle Support Banner

Portuguese Localization - Software Certification Electronic Encrypted Signature for Invoices (Doc ID 2382188.1)

Last updated on AUGUST 24, 2020

Applies to:

Oracle Fusion Receivables Cloud Service - Version and later
Information in this document applies to any platform.


As part of an Anti-fraud Commercial documents Law, Portugal Govt requires
that each commercial document (invoice or shipment) must be assigned an
electronic/encrypted signature using Asymmetric RSA Encryption Algorithm (SHA-1 or SHA-2)

a) Encryption Signature should include (by concatenating):
1) Invoice Date
2) System Entry Date
3) Invoice Number
4) Invoice Amount
5) Signature of the previous document

b) Generate the encryption signature for the following types of Receivables
1) Sales Invoice
2) Credit Memo
3) Debit Memo
4) Deposit
5) Guarantee
6) Charge-back

c) All billing invoices must be reported as part of SAF-T (Standard Audit
File for Tax purpose), regardless of where they were issued, along with their
original electronic signature;

d) Externally created/generated invoices with encrypted signature generated
outside Oracle ERP must be imported ´as is´. Software shouldn't regenerate
the signature;

e)At the time of completion of the invoice or similar document, the
electronic signature should be generated and saved to the database using the
RSA encryption algorithm;

f) Completed invoices should not allowed to be modified;

g) Invoice errors should be corrected using a Debit Memo or Credit Memo, if
that is not possible it should be voided with a Credit Memo and the
transaction will be billed again;

h) Transactions Incomplete will be allowed only when transaction type is
either Bills Receivables or Receipts



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.