XSD for SBA_ETran 9.2, Origination. Revised Publication Date: 04/30/2026. To view the full content, you must right click the page and select "View Page Source". General Information The following XSD documents <SBA_ETran version="9.1"> and its subelements for the Originate3, Originate4, OrigScore, OrigUpdate and Underwriting web service methods. (OrigBypass doesn't allow XML changes.) When creating a new loan application (Originate3/4 and OrigScore), missing elements are treated as having no value (also known as null or nullstring). But when updating an existing loan application (OrigUpdate and Underwriting), missing elements are treated as requiring no change from the existing data already received by the SBA. This is true both at the group level and individual data element level. For example, if no special purpose changes are needed, it is not necessary to give any <SpecialPurpose> elements at all, even though one would normally need to give at least NOSP when creating a new application. When updating an existing loan application, the absence of <SpecialPurpose> elements simply means that none of them changed. For this reason, LoanApplication, Borrower, Interest, Principal, PrincipalRace, SpecialPurpose and UseOfProceeds are now all identified as optional (minOccurs="0"). But the need to give these elements when creating a new application is the same as always. Except for elements used as prime keys to identify which data entity is to be updated, and except for ProcessingMethodCd, LocationId and changing UnderwritingBy from SBA back to LNDR, any element that a submitter has role and permissions to give when creating a new application, that same element can also be updated using version 4.0 and up. Versions 4.0 and up give OrigUpdate and Underwriting the same full updating capability that the SBA web pages have. Specifics about the few elements that remain unchangable when updating an existing application are given in the XML comments that immediately follow those elements in this XSD. New Predeletion Feature when Updating an Existing App (action="deleteall") It may not be possible for some users of OrigUpdate or Underwriting to completely track what changes have been made to an application. In such situations, and for some complexTypes, it may be possible to "predelete" all data associated with a complexType and simply re-insert the elements as they are now, starting over from scratch. When updating an existing app, versions 4.0 and up now allow the first action attribute of some complexTypes to be "deleteall", provided that all subsequent action attributes of the same complexType are "insert". In database jargon, this is sometimes referred to as "delete-and-insert logic". For example: <SpecialPurpose action="deleteall"/> <SpecialPurpose action="insert"><SpcPurpsLoanCd>ITRD</SpcPurpsLoanCd></SpecialPurpose> <SpecialPurpose action="insert"><SpcPurpsLoanCd>REVL</SpcPurpsLoanCd></SpecialPurpose> In this example, it's guaranteed that all pre-existing SpecialPurpose data will have already been deleted at the time the inserts are saved. There are pros and cons to using delete-and-insert logic, of course. The pros are eliminating the need to track what already exists on the SBA's Origination database and no longer having to individually delete no-longer-applicable data. The cons are having to re-insert data that had already been inserted and having a larger XML file size as a result. This exact pattern above ("deleteall" first, all the rest "insert") is the only way the predeletion feature can function properly. For this reason, it's not good enough for "deleteall" to be allowed by the xs:attribute's type for the action. It must also be used only in the first occurrence of the complexType within the "App", following the pattern above. Otherwise, the predeletion feature is disabled (for that complexType) and all the old rules for updating an existing app apply (the prime key must exist for "delete" and "update" or must not exist for "insert", if allowed by the type). Not all complexTypes support action="deleteall". For this reason, be sure to read the comments associated with the action attributes below. Alternatively, be sure you have the most current version of SBA_ETranTypes.xsd and look there to see whether or not "deleteall" is enumerated for the action's type. The SBA's "root tag" (<SBA_ETran>) for Origination must contain at least one <App> tag. It may contain more than one. If more than one <App> tag is given, each <App> tag will commit to the SBA's database, or roll back from it, independently of all other <App> tags in the same submission. For this reason, <App> is sometimes referred to as the "transaction tag" of Origination. ExtractOrigination may optionally generate this attribute. It is ignored by Originate3, OrigScore, OrigUpdate and Underwriting. It is defined in the XSD solely to prevent validating parser errors. ExtractOrigination may optionally generate this attribute. It is ignored by Originate3, OrigScore, OrigUpdate and Underwriting. It is defined in the XSD solely to prevent validating parser errors. Your "root tag" should be <SBA_ETran version="7.1"> for XML that conforms to this XSD. See SBA_ETranTypes.xsd for an explanation of ETran version numbers and their coding implications.