G-Invoicing System Integration Guide
evening, followed by a call to pull only Orders in REC (open) status. That agency could compare those
two lists to what they have on file, making updates as needed. If a known Order falls off both of these
lists, it can be assumed that no further action is required for that Order. If a new Order appears on the
SP2 list, the agency client may then pull the entire Order.
An agency client could choose to pull a list of all documents of a specific type (e.g., GT&C), although
this is not recommended. That list will contain all GT&C agreements for that agency, regardless of status.
That means that closed GT&Cs will be on the list, no matter how old they are. Obviously, such a list can
grow very large, depending on the age of the system and the number of documents handled annually.
2.5.5 Attachments on Demand
Data retention policies have not yet been established, but G-Invoicing will not delete data or attachments
until such policies are defined and the customer base is alerted. Agencies may choose to rely on G-
Invoicing to store complete document data and attachments so they can be accessed only when needed.
For example:
• Metadata describing the existence of an attachment (e.g., file name, size, type, URL) can be saved
in an agency system so that a specific attachment can be retrieved by an agency user on demand.
• Data describing the existence of a GT&C agreement (e.g., GT&C number, title, status, URL) can
be saved in an agency system so a user of that system may select a valid GT&C from a drop-
down list or search facility. If that agency user wishes to view the full GT&C, it can be retrieved
from G-Invoicing by the agency system at that time.
Relying on G-Invoicing to store complete document data and attachments will reduce an agency’s data
and file storage requirements, but may greatly increase system-to-system communications with G-
Invoicing if that information is repeatedly requested. Agencies (and their vendors) are encouraged to use
their best judgement when designing a solution.
2.5.6 Groups on Demand
Agency systems submitting Orders to G-Invoicing will need to know what organizational Groups and ALCs may
be assigned to an Order, based on the Group assigned to the GT&C. The Pull Organization API provides this
information and can be accessed in four ways:
1. Once a GT&C is pulled for the first time or after a change, the requesting and servicing Groups eligible to
use that GT&C to create Orders may be obtained. The list returned is static, however, and changes made
later to the descendant Groups (e.g., new Group, inactivated Group) will not be known.
2. Groups eligible for each open GT&C may be pulled on a periodic basis to account for organizational
changes otherwise not known.
3. The Pull Org API allows agencies to pull down entire organizations, to which rules may be applied to
determine Groups eligible to use a GT&C to create Orders. This too must be refreshed periodically to
account for organizational changes otherwise not known.
4. The Pull Org API may be accessed in real-time to support a user of an agency system attempting to create
an Order that will eventually be sent to G-Invoicing. The Groups returned are guaranteed to work for an
Order, and contain the TAS filters G-Invoicing uses to validate TAS.
If necessary, the new Order can be assigned to the same Group as the GT&C, although TAS filters may vary
between Groups.