Get invoice

Action ID

actions.intent.GET_INVOICE

Description

Present a user's bill or invoice. Determine what invoice the user is requesting or present multiple items, if applicable.

We recommend that you specify entities for invoice.forService.name.

Locale support

Functionality	Locales
Preview creation using App Actions test tool	en-US, en-GB, en-CA, en-IN, en-BE, en-SG, en-AU, es-ES, pt-BR
User invocation from Google Assistant	en-US, en-GB, en-CA, en-IN, en-BE, en-SG, en-AU, es-ES, pt-BR

Example queries

en-US, en-GB, en-CA, en-IN, en-BE, en-SG, en-AU

• Get ExampleProvider bill.
• ExampleProvider June credit card bill.
• Show me my current bill using ExampleProvider.
• Open up my mortgage statement using ExampleProvider.

es-ES

• Busca la factura del teléfono en ExampleProvider.
• Dime en ExampleProvider cuándo se vence la factura del cable.
• Muestra la fecha en que vence el recibo en ExampleProvider.
• Ver la factura de la luz con ExampleProvider.

pt-BR

• Usar ExampleProvider para ver como é cobrada minha conta da Sky.
• Use o ExampleProvider para ver os vencimentos das minhas contas desse mês.
• Consultar vencimento da conta de luz pelo ExampleProvider.

Other supported fields

The following fields represent information that users often provide to disambiguate their needs or otherwise improve their results:

invoice.@type
invoice.forService.@type
invoice.forService.name
invoice.forService.provider.@type
invoice.forService.provider.name

Supported text values by field

invoice.@type

• Invoice

invoice.forService.@type

• Service

invoice.forService.provider.@type

• Organization

Inventory availability by field

invoice.forService.name

• Inline inventory

invoice.forService.provider.name

• Inline inventory

Sample XML files

For information about the actions.xml schema, see Create actions.xml. For information about the shortcuts.xml schema, see Create shorcuts.xml.

Handle BII parameters

shortcuts.xml

<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample shortcuts.xml -->
<shortcuts xmlns:android="http://schemas.android.com/apk/res/android">
  <capability android:name="actions.intent.GET_INVOICE">
    <intent
      android:action="android.intent.action.VIEW"
      android:targetPackage="YOUR_UNIQUE_APPLICATION_ID"
      android:targetClass="YOUR_TARGET_CLASS">
      <!-- Eg. forServiceName = "Utility" -->
      <parameter
        android:name="invoice.forService.name"
        android:key="forServiceName"/>
      <!-- Eg. providerName = "Example Provider" -->
      <parameter
        android:name="invoice.forService.provider.name"
        android:key="providerName"/>
    </intent>
  </capability>
</shortcuts>
      

actions.xml

<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample actions.xml -->
<actions>
  <action intentName="actions.intent.GET_INVOICE">
    <fulfillment urlTemplate="myapp://custom-deeplink{?forServiceName,providerName}">
      <!-- e.g. forServiceName = "Utility" -->
      <!-- (Optional) Require a field eg.forServiceName for fulfillment with required="true" -->
      <parameter-mapping urlParameter="forServiceName" intentParameter="invoice.forService.name" required="true" />
      <!-- e.g. providerName = "Example Provider" -->
      <parameter-mapping urlParameter="providerName" intentParameter="invoice.forService.provider.name" />
    </fulfillment>

    <!-- Provide a fallback fulfillment with no required parameters. For example, to your app search or router deeplink -->
    <fulfillment urlTemplate="myapp://deeplink" />
  </action>
</actions>

Use inline inventory

shortcuts.xml

invoice.forService.name is an intent parameter that supports inline inventory. By defining a <shortcut> for invoice.forService.name, you can uniquely identify entities that are of interest to your app or restrict fulfillment to the set of supported entities.

In the following example, when the user query matches the forServiceName_one shortcut, Assistant provides the associated shorcut identifier, ID_ONE, as the URL parameter forServiceName to fulfillment.

If there is no inventory match, the text value received in the query for invoice.forService.name is passed as-is.

<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample shortcuts.xml -->
<shortcuts xmlns:android="http://schemas.android.com/apk/res/android">
  <capability android:name="actions.intent.GET_INVOICE">
    <intent
      android:targetPackage="YOUR_UNIQUE_APPLICATION_ID"
      android:targetClass="YOUR_TARGET_CLASS">
      <parameter
        android:name="invoice.forService.name"
        android:key="forServiceName"/>
      <parameter
        android:name="invoice.forService.provider.name"
        android:key="providerName"/>
    </intent>
    </capability>
    <!-- Short and long labels must be @string resource. -->
    <shortcut
      android:shortcutId="ID_ONE"
      android:shortcutShortLabel="@string/shortcut_short_label"
      android:shortcutLongLabel="@string/shortcut_long_label">
      <capability-binding android:key="actions.intent.GET_INVOICE">
        <parameter-binding
          android:value="forServiceName"
          android:key="invoice.forService.name"/>
      </capability-binding>
    </shortcut>
</shortcuts>
      

actions.xml

invoice.forService.name is an intent parameter that supports inline inventory. By defining an <entity-set> for invoice.forService.name, you can uniquely identify entities that are of interest to your app or restrict fulfillment to the set of supported entities.

In the following example, when the user query matches the forServiceName_one entity, Assistant provides the associated identifier, ID_ONE, as the URL parameter forServiceName to fulfillment.

If there is no inventory match, the text value received in the query for invoice.forService.name is passed as-is.

<?xml version="1.0" encoding="utf-8"?>
<!-- This is a sample actions.xml -->
<actions>
  <action intentName="actions.intent.GET_INVOICE">
    <fulfillment urlTemplate="myapp://deeplink{?forServiceName}" >
      <!-- forServiceName = "ID_ONE" or "ID_TWO"  -->
      <!-- If no inventory match, forServiceName is a text value, such as "Utility" -->
      <!-- (Optional) Use entityMatchRequired="true" to require inventory match for fulfillment -->
      <parameter-mapping urlParameter="forServiceName" intentParameter="invoice.forService.name" />
    </fulfillment>

    <!-- Define parameters with inventories here -->
    <parameter name="invoice.forService.name">
      <entity-set-reference entitySetId="forServiceNameEntitySet"/>
    </parameter>
  </action>

  <entity-set entitySetId="forServiceNameEntitySet">
  <!-- Provide an identifier per entity -->
    <entity identifier="ID_ONE" name="forServiceName_one" alternateName="@array/forServiceName_one_synonyms"/>
    <entity identifier="ID_TWO" name="forServiceName_two" alternateName="@array/forServiceName_two_synonyms"/>
  </entity-set>
</actions>

The url attribute associated with the entity can be used to determine the fulfillment URL if there is an inventory match. In the following example, when the user query matches the forServiceName_one entity, Assistant provides myapp://deeplink/one as the fulfillment URL.

  <?xml version="1.0" encoding="utf-8"?>
  <!-- This is a sample actions.xml -->
  <actions>
    <action intentName="actions.intent.GET_INVOICE">
      <!-- Use url from inventory match for deep link fulfillment -->
      <fulfillment urlTemplate="{@url}" />

      <!-- Provide a fallback fulfillment with no required parameters. For example, to your app search or router deeplink -->
      <fulfillment urlTemplate="myapp://deeplink" />

      <!-- Define parameters with inventories here -->
      <parameter name="invoice.forService.name">
        <entity-set-reference entitySetId="forServiceNameEntitySet"/>
      </parameter>
    </action>

    <entity-set entitySetId="forServiceNameEntitySet">
      <!-- Provide a URL per entity -->
      <entity url="myapp://deeplink/one" name="forServiceName_one" alternateName="@array/forServiceName_one_synonyms"/>
      <entity url="myapp://deeplink/two" name="forServiceName_two" alternateName="@array/forServiceName_two_synonyms"/>
    </entity-set>
  </actions>
  

JSON-LD sample

The following JSON-LD sample provides some example values that you can use in the App Actions test tool:

{
  "@context": "http://schema.googleapis.com",
  "@type": "Invoice",
  "forService": {
    "@type": "Service",
    "name": "Utility",
    "provider": {
      "@type": "Organization",
      "name": "Example Provider"
    }
  }
}