Saasu Integration : Generate Invoice Number

When we build an integration with Saasu, you may need to create Invoice/PurchaseOrder. How do you generate the correct Invoice/Purchase Order Number? There are two ways of achieving this:

Method  1: Use Auto Number

Instead of putting the invoiceNumber manually, you can let Saasu decide the latest invoiceNumber. This behavior is applicable to Purchase Order too. Your request will look like this:

<tasks>
  <insertInvoice>
    <invoice uid="0">
      ...
      <invoiceNumber>&lt;Auto Number&gt;</invoiceNumber>
      ...
    </invoice>
  </insertInvoice>
</tasks>

By using this feature, you should not create duplicate Invoice/Purchase Order.

Method 2: Maintain unique Invoice/PurchaseOrder number in another system

This scenario is applicable if you are integrating Saasu with another system. For example: If you are integrating Saasu with Salesforce, you can use Salesforce Auto-Number custom field to generate the Invoice/PurchaseOrder number. Salesforce will take the responsibility of maintaining the unique Invoice/PurchaseOrder number.

Saasu – Company information via the API

If you are using Saasu and looking to integrate with Salesforce or a CRM that has a Company object, you’ll need to handle this differently with Saasu.  With the Saasu API you are able to create/update a Contact’s Company information via the Contact page as Company in Saasu is not a separate object.
 –> 
To retrieve or create the Company information, we can do this via the Contact Object. In a Contact profile, Saasu utilizes the following elements to associate with the Contact’s Company:
organisationName, organisationAbn, organisationWebsite
Following is an example of a insertContact Request profile which consist of the Company information (see the bold section):
<?xml version=”1.0″ encoding=”utf-8″?>
<tasks>
  <insertContact>
    <contact uid=”0″>
      <salutation>Mr.</salutation>
      <givenName>John</givenName>
      <familyName>Smith</familyName>
      <organisationName>Saasy.tv</organisationName>
      <organisationAbn>777888999</organisationAbn>
      <organisationPosition>Director</organisationPosition>
      <email>john.smith@saasy.tv</email>
      <mainPhone>02 9999 9999</mainPhone>
      <mobilePhone>0444 444 444</mobilePhone>
      <contactID>XYZ123</contactID>
      <tags>Gold Prospect, Film</tags>
      <postalAddress>
        <street>3/33 Victory Av</street>
        <city>North Sydney</city>
        <state>NSW</state>
<postCode>2000</postCode>
        <country>Australia</country>
      </postalAddress>
      <otherAddress>
        <street>111 Elizabeth street</street>
        <city>Sydney</city>
        <state>NSW</state>
<postCode>2000</postCode>
        <country>Australia</country>
      </otherAddress>
      <isActive>true</isActive>
      <acceptDirectDeposit>false</acceptDirectDeposit>
      <directDepositAccountName>John Smith</directDepositAccountName>
      <directDepositBsb>000000</directDepositBsb>
      <directDepositAccountNumber>12345678</directDepositAccountNumber>
      <acceptCheque>false</acceptCheque>
      <customField1>This is custom field 1</customField1>
      <customField2>This is custom field 2</customField2>
      <twitterID>Contact twitter id</twitterID>
      <skypeID>Contact skype id</skypeID>
      <saleTradingTerms>
        <type>1</type>
        <interval>7</interval>
        <intervalType>1</intervalType>
      </saleTradingTerms>
      <purchaseTradingTerms>
        <type>2</type>
        <interval>14</interval>
        <intervalType>1</intervalType>
    </purchaseTradingTerms>
    <defaultSaleDiscount>15.75</defaultSaleDiscount>
    <defaultPurchaseDiscount>12.50</defaultPurchaseDiscount>
    </contact>
  </insertContact>
</tasks>
For example, when creating/updating a Contact, the operation would use the organisationName value to find for matching Company Name and if there is no match, the defined Company will be created in Saasu instead.

Get the popcorn, sit back, relax and watch our videos.

Sure, they are not going to win any Oscars, but if you’re interested in Salesforce integration to 2 of the most popular accounting packages around, take a look at our Salesforce to Saasu and Salesforce to MYOB ReadyMade integration solutions.  Oh and yeh, you won’t need a big bowl of popcorn cos they only last a few minutes each.

weblinc implements the Salesforce-Saasu ReadyMade

It’s great to announce a case study with one of our new customers, weblinc.

weblinc engaged WDCi to build and deploy a rapid integration process between salesforce.com and Saasu. We recommended that weblinc employ our ReadyMade Salesforce CRM/ Saasu Widget in order to get into production, fast.

weblinc now has available an automated bi-directional sync of data between Salesforce and Saasu.

The full case study can be found here.

Productized integration processes – are we crazy?

I’m going to go out on a limb here and say that you can productize specific business processes into a packaged integration solution.

This is something that regularly perplexes die-hard integration architects and at the opposite end of the spectrum regularly astounds SMEs when they find out there aren’t pre-built integrations between every application.

Who needs it?

SMEs now have access to tools and products at a fraction of the price they were years ago.  They can have best of breed solutions to run their business, BUT, who can afford to pay for a custom integration solution to integrate their data?  The applications are bleeding edge, but it doesn’t save you time and money if they aren’t in sync.

How to do it?

Our approach to this is ReadyMade, pre-built integration solutions that solve standard integration requirements between common applications.

Some history

We thought that there has to be some common business processes between applications.  So we spent some time looking at applications we know well, like salesforce.com.  We then looked at what accounting packages people use to connect to Salesforce and discovered that MYOB and Saasu were very popular in the Salesforce community in this part of the world.

So, we then took a look at how customers use MYOB on-premise and how they use Saasu in the cloud and used these observations to determine if there were common functions and processes that could be automated to save time and money.

And of course there are common processes that if integrated would provide the biggest bang for buck.

Don’t get me wrong, it isn’t easy to first work out the common integration processes, identify the right tool, develop the solution, price it right, market it, sell it and then back it up with support.

Well why do it?

Because we like to solve problems in the simplest way possible and we see the potential of SaaS but we also understand the role of existing applications to a company.  Let’s not fix something that isn’t broken.

The end result

Our ReadyMade solutions allow an SME to run the best of breed applications without the need to re-key data or deal with data inconsistencies and errors.

They don’t solve every integration process, they’re not meant to, that’s what custom integration solutions are for, they simply provide a productized integration for standard business processes between 2 defined applications and they do it at a low-cost.

Salesforce-Saasu ReadyMade update

The Salesforce to Saasu RIO ReadyMade integration solution now includes payment information updated to Salesforce.  Here’s the new application integration process flow:

Looking for more details, check out the product documentation or contact us.

Thanks to www.dryicons.com for the above people icon.